In Clayton, a tracked branch refers to a branch in a Git repository that is monitored by Clayton to automatically trigger scans. Clayton gives you option to fine tune when and how your pull request (PR) scans are triggered. One of the most useful features here is the ability to limit scans to tracked branches, a great way to reduce noise and improve performance if you have lots of PRs flying around.
​
When you set up a new project you will get the option to Choose your preferred protection scheme. Here you can choose to Scan PRs only when destination is a tracked branch.
​

Under Protect what's new → More options, and you’ll find the setting Scan PRs only when destination is a tracked branch:
​

Enable this option if you want Clayton to only scan pull requests targeting branches you've explicitly marked as “tracked.”

Head to your Repository Settings in Clayton, click the Protection tab, and then select the Change button.

This will open up a series of options that control how and when Clayton runs its scans on incoming pull requests.

If you select the repository that you would like to track you can select the drop down menu and here you can see which branches are tracked and which are not. By selecting the untacked branch and then selecting the toggle button beside the deop down menu you can change to branch to being track. Alternatively you do the same process to untrack branches.
​

​
Why Use This

Using this helps improve performance by avoiding unnecessary scans on experimental or short-lived feature branches. It reduces noise by keeping scan reports focused on production-critical flows and ensures teams stay aligned by running compliance checks only where they’re truly needed.