Configure a Codacy Quality Gate for Pull Requests
Block pull requests that introduce new lint violations or security findings by configuring a Codacy quality gate and requiring its status check before merge.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Block pull requests that introduce new lint violations or security findings by configuring a Codacy quality gate and requiring its status check before merge.
Diagnostic guide for SonarQube Java analysis that succeeds but shows zero or missing new-code issues.
When Qodana quality gates fail in CI, the culprit is often a mis‑configured threshold or a mismatch between local and CI settings. This guide walks through the recognizable symptoms, diagnostic checks, and targeted fixes to get builds passing again.
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.
Learn how to configure SonarQube 'New Code' definitions to implement effective Quality Gates that focus on recent changes without being overwhelmed by legacy technical debt.
Discover how SonarQube’s Compute Engine separates scanner output from database updates, and learn how to size, configure, and monitor it to keep CI pipelines responsive.
Learn how to configure SonarQube's Leak Period so that quality gates only flag issues introduced after a reference point, reducing noise from legacy debt.
Introducing SonarQube to a legacy Java codebase without blocking delivery: scope Quality Gate conditions to New Code, wire JaCoCo coverage, and verify the gate actually blocks CI.
Learn how to configure SonarQube's Quality Gate to evaluate only New Code, enabling the Clean as You Code strategy in a typical CI pipeline with Maven and GitHub Actions.