Managing Technical Debt with PhpStorm Inspection Profiles
Learn how to use PhpStorm Inspection Profiles to silence legacy code noise and enforce strict static analysis on new PHP features without overwhelming your workspace.
Loading…
ReadMeFeed / Community knowledge
#code-quality
Real questions. Useful conversations. Find the people who know your stack.
phpstormQuality Gates as a Merge Gate: Using SonarQube New Code to Protect Forward Progress
Use SonarQube Quality Gates scoped to New Code to turn code quality metrics into an enforced merge decision without blocking delivery on legacy debt.
Preventing Code Decay with Qodana Quality Gates
Stop the 'slow leak' of technical debt. Learn how to use Qodana Quality Gates to prevent code regressions by comparing CI analysis against a stable baseline.
qodanaESLint warn severities and the CI --max-warnings gate: advisory alerts or errors-only policy?
ESLint documents three per-rule severities — off , warn , and error — set in eslint.config.js (flat config, the default in ESLint v9+) or a legacy .eslintrc file. The intent is that error fails the run while warn surfaces advisory findings, letting teams introduce new or stylistic rules without breaking existing code. The friction sits between the two integr
eslint
php