Create a quality gate with GitHub

Learn how to create a quality gate that will only let merge code that passes Clayton's reviews.

Lorenzo Frattini avatar
Written by Lorenzo Frattini
Updated over a week ago

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 merged

Before to start

Before proceeding 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.

GitHub App

Please have a look at our Help Article to learn how to set up our official app.

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.


  1. In your repository settings in GitHub, go under Settings  > Branches

  2. In the Branch protection rules section, click on Add rule

  3. In the Branch name pattern field, type the branch name you would like to create the gate for

  4. Make sure to have at least 1 Required approving reviews

  5. Require Clayton's status checks to pass before merging

  6. Click on Save changes


The Require status check can be selected if you want to prevent merging if the entire branch from where the PR has been generated doesn't respect the quality standards defined in Clayton.

Did this answer your question?