You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now there is no way to manage protected branches via wildcards (e.g. release/*), and we need to scan our feature branches for new vulnerabilities when a PR is opened up with a release branch. The only option for managing protected branches that I have found is through the web UI so this becomes very tedious when dealing with a fast release cycle as the number of projects grows.
Propose a solution
I would like a CLI command for retrieving the current protected branches set for a project, as well as the ability to add or remove protected branches from that list.
Additional comments
The option to set protected branches using wildcards would be another solution to the problem I am facing but I'm not sure if that is a viable solution on the back end.
The text was updated successfully, but these errors were encountered:
Is your request related to a workflow problem?
Right now there is no way to manage protected branches via wildcards (e.g. release/*), and we need to scan our feature branches for new vulnerabilities when a PR is opened up with a release branch. The only option for managing protected branches that I have found is through the web UI so this becomes very tedious when dealing with a fast release cycle as the number of projects grows.
Propose a solution
I would like a CLI command for retrieving the current protected branches set for a project, as well as the ability to add or remove protected branches from that list.
Additional comments
The option to set protected branches using wildcards would be another solution to the problem I am facing but I'm not sure if that is a viable solution on the back end.
The text was updated successfully, but these errors were encountered: