For the complete documentation index, see llms.txt. This page is also available as Markdown.
Overview
An overview of the improving code quality process.
For each project, the improving code quality implementation looks like this:
First, you define the quality standard for your project:
With a quality profile, you define the set of rules to be applied during analysis.
With a quality gate, you define a set of conditions that the code must meet.
Then, you define what is considered new code in your project, adapting your configuration to the nature of your project: versioned, continuous delivery, etc.
Finally, you ensure your code is analyzed frequently and at different stages of its journey, in your IDE and your DevOps platforms.
Improving code quality as a developer
The configuration steps described above and in the following sections are handled by project administrators. As a developer, you improve code quality by reviewing and fixing the issues detected in new code, ensuring that the quality gate is always green and that only production-ready code is merged.
To learn more about these topics, refer to the Issues, Quality gates, and Software qualities sections (see links below).
