Which branch does Snyk Monitor

Today Snyk monitors the default branch. So if a repo is set to point at `develop` by default then Snyk would do pull requests against `develop`.

If you require Snyk to test a non-default branch, we have an implementation of this functionality
available. It’s currently in closed Beta behind a feature flag while it is being developed. If you want to be involved in the beta email support@snyk.io and let us know.

How to use our custom branch feature

Once we’ve enabled the flag, you will be able to test non-default branches of projects. To do
this, go through the Add Projects flow for your chosen source code manager (in this example,
we’re using GitHub), and you’ll see a new option to monitor a branch.

Below you can see the field where the branch can be specified only once the flag has been enabled. Again, if you're interested in this feature please contact our support team.

Screen_Shot_2022-06-09_at_11.09.16_AM.png

If a single branch is monitored, there will be a single project for each detected manifest file.

Screen_Shot_2022-06-09_at_11.11.23_AM.png

If we go through through the same Add Project flow, but this time with a different branch, and Snyk
detects manifest files in that, I will see additional projects listed under the same repo.

Screen_Shot_2022-06-09_at_11.11.37_AM.png

It’s worth bearing this in mind if you have repos with dozens of manifest files, because each
manifest file on each branch generates a separate project.

This is particularly important when considering commit statuses, because each monitored
branch will generate a separate commit status.

Future plans

We are currently working on improvements to our branch support feature before we release this
to everyone. The first version will allow anyone to monitor any single branch on their app
(custom branches). The second version will allow anyone to monitor multiple branches of the
same app (multiple branches).

Articles in this section

How to use our custom branch feature

Future plans