ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Choose between IntelliJ’s fast inline inspections and SonarQube’s cross-project quality metrics. This guide outlines constraints, trade-offs, and a validation workflow for Java teams.
Implement SonarQube Quality Gates to automatically fail CI/CD builds when new code breaches thresholds for bugs, vulnerabilities, or coverage.
Learn how to integrate Qodana into GitHub Actions, output SARIF, and view results in Code Scanning. Includes a minimal workflow, a sample .qodana.yml, and tips for avoiding common pitfalls.
Use Qodana baselines to freeze existing technical debt and gate CI on new issues only, enabling incremental quality improvement without blocking merges on legacy violations.
Add Qodana to your CI with a single workflow file, cache results for speed, and push SARIF to GitHub Code Scanning. Learn the exact steps, pitfalls, and how to verify the output.
Configure SonarScanner to wait for the Quality Gate and fail your pipeline when new-code issues violate the gate, then verify with a deliberate violation.
Decide whether Qodana full scan, baseline, or Cloud mode should fail CI on new Java/Kotlin static-analysis issues, with config examples and verification steps.
Guide to tell when Codeac’s hardcoded‑secret warning is a false positive in Java test code and how to safely suppress or fix it.
Dart's Sound Null Safety moves null errors to compile time, but the `!` and `late` escape hatches can reintroduce runtime crashes. Here is how to use them safely.
intellij
java
sonarqube
qodana