Today Snyk monitors the default branch. If a repository is set to point to `main` by default then Snyk will import and monitor this branch. Fix pull requests would be opened against `main` as well.
If you want to use Snyk to test a non-default branch, we have an implementation of this functionality available. It’s currently in closed Beta while it is being developed. If you would like to be added to the beta, please open a support ticket or email support@snyk.io and let us know.
Closed Beta
This feature is currently under Closed Beta.
For more information please see this article: Snyk Closed Beta Features
How to use our custom branch feature
Once we’ve enabled the feature, you will be able to import and 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 once the flag has been enabled.
If a single branch is monitored, there will be a single Project for each detected manifest file.
If we go through the same Add Project flow, but this time with a different branch, and Snyk
detects manifest files in that, I will see multiple collapsible sections with Projects listed under the same repo.
It’s worth bearing this in mind if you have repositories 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 before this feature is released as GA.