Overview

For each project, the Clean as You Code 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. 

Practicing Clean as You Code as a developer

The configuration steps described above and in the following sections are handled by project administrators. As a developer, you practice Clean as You Code by reviewing and fixing the issues detected in new code, ensuring that the quality gate is always green and that only clean code is merged. 

To learn more about these topics, refer to the Issues, Quality gates, and Clean Code sections (see links below).

Related pages

• Setting up Clean as You Code
• Issues
• Quality gates
• Clean Code