ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Scope SonarQube Quality Gates to new code so legacy issues do not block modern pull requests.
Use SonarQube Quality Gates to enforce standards on new code without being blocked by legacy debt.
Implement SonarQube Quality Gates to automatically fail CI/CD builds when new code breaches thresholds for bugs, vulnerabilities, or coverage.
A decision guide for choosing between SonarQube's date-based and SCM-based leak periods. Covers constraints, a comparison table, trade-offs, and a concrete CI validation procedure using a controlled code change to verify new-code detection accuracy.
Use SonarQube Quality Gates to enforce code quality thresholds in CI/CD. Learn how to set up gates, integrate them into GitHub Actions, understand trade‑offs, and verify results locally.
Enforcing SonarQube Quality Gates on Overall Code blocks builds on legacy debt. Configure conditions against New Code metrics and use sonar.qualitygate.wait=true so CI fails only on recent changes.
Learn how SonarQube Quality Gates enforce pass/fail thresholds, how to configure conditions and make your CI pipeline wait for the result, plus common pitfalls.
Learn how to configure and use SonarQube Quality Gates to enforce thresholds like bug count and coverage, with a step‑by‑step example, limits, and common pitfalls.
Qodana's failureConditions in qodana.yaml let you cap problems by severity so the CI job fails and the merge is blocked when limits are exceeded.
sonarqube
qodana