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.
Loading…
ReadMeFeed / Community knowledge
#quality-gate
Real questions. Useful conversations. Find the people who know your stack.
SonarQube analysis returns SUCCESS but reports zero issues
Diagnostic guide for SonarQube Java analysis that succeeds but shows zero or missing new-code issues.
sonarqubeDiagnosing and Fixing Qodana Quality Gate Failures in CI Pipelines
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.
qodanaSonarQube New Code Definitions: A Practical Guide for CI/CD Quality Gates
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.
Using SonarQube Leak Period to Isolate New Code Issues in CI
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.
Gating New Code, Not History: Adopting SonarQube Without a Legacy Cleanup Sprint
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.
javaUsing SonarQube's New-Code Quality Gate to Enforce Clean as You Code
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.
Enforcing Build Failures with SonarQube Quality Gates
Learn how to configure SonarQube Quality Gates to automatically fail CI/CD builds when new code violates security or quality thresholds.