ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Configure Qodana EAP with --threshold=WARN to automatically fail builds when code quality issues exceed acceptable levels. This guide covers GitHub Actions integration, memory tuning, and common pitfalls.
Stop technical debt from leaking into your codebase. Learn how to use SonarQube Quality Gates to automate 'stop-the-line' decisions in your CI/CD pipeline.
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.
Learn how to tune Qodana inspections with a custom .qodana.yml file and publish an HTML report to the Qodana dashboard from a GitHub Actions workflow.
A guide to selecting the right refactoring tool in PHPStorm, comparing Rename, Find and Replace, and Structural Search strategies.
Close the gap between IDE inspections and CI by running Qodana locally via its CLI. Learn the prerequisites, qodana.yaml setup, and how to verify results.
Stop fighting your linter in callback-heavy projects. Learn how to configure ESLint's no-unused-vars rule to ignore API-mandated function parameters while still catching actual variable leaks.
Qodana baselines let teams commit the current violation set as an accepted floor, then fail CI only on new issues—enabling incremental quality adoption without halting delivery.
Legacy codebases drown new Qodana violations. Learn how Baseline snapshots current issues, lets CI diff against them, and only fails on fresh quality problems.
qodana
phpstorm
eslint