Click Code Reviews, then click Issues, and select your repository from the selector at the top.
Click the three-dot menu next to the repository selector, then click Settings.
Open the Rules tab. The left menu also has Tracked Branches, Configuration, and Ignore List.
Find the rule you want to change. Use its toggle to turn it on or off, or use its severity dropdown to change the severity.
The first time you change a rule, Gearset shows a warning. It explains that editing a rule combines your existing Clayton policies into a single policy.If you have previously set up status check gates in your VCS, you will need to update the name of the check to maintain your gate.
What do the severity levels mean?
Code Reviews rules have three severities: Critical, Error, and Warning. Change a rule's severity from the Rules tab, using the severity dropdown next to the rule.
A rule's severity doesn't decide whether a pull request can merge. Code Reviews only blocks a merge when you set up a quality gate for it in your version control system, and that's a separate, deliberate step.
Severity does control which issues show as individual comments on a pull request, when Publish individual comments for issues is turned on. A newly connected repository starts with Critical and Error switched on, and an existing repository keeps commenting on every severity. Turning a severity off only removes its comments. The review outcome, the status check, and the issue counts in the summary comment still cover every severity, whatever the comment switches are set to.