What is a quality gate?
A quality gate is the best way to enforce a quality policy in your organization. Setting up a quality gate allows you to prevent any code that doesn't pass code reviews, from being merged into certain branches.
Key Benefits
Enforce code quality consistency across the entire project
Ensure that newly committed code doesn't introduce problems
Ensure issues are addressed before being merge
Before to start
Before proceed with creating a quality gate in your VCS for your repo, you must enable Clayton Automation and create a dedicated Clayton connection user for your project.
Enable Automation
Make sure to activate the Clayton Automation to monitor your code and start using webhooks to publish status updates for the PR and branch reviews on your VCS.
Please have a look at the dedicated Help Article to learn how to enable automation.
Configure Clayton as a required approval for your merge requests
Got to GitLab > your repo General settings
Expand the Merge request approvals section
Select Add approval rule or Update approval rule
Add the Clayton connection user to the Approvers (do you need to set up a dedicated Connection for Clayton? You can read more here)
Make sure the Approvals required field is set at least to 1
Click on Save changes
See the official GitLab documentation here.
