Pull Request Branch Filter/restriction
Currently creating a pull request from the "Create pull request Screen" provides the user with a list of all the branches.
The default of this seems to be based on the last location you had selected when you created your branch (This usually ends up being main). As we have a pipeline this is the last place you want anyone being able to create a PR into!
It would be great if we could whitelist/blacklist a bunch of Branch names on this dropdown to stop users accidentally selecting main when creating a PR (for most users this would be one branch)
As when this happens we end up having to get them to re-do the while PR (As reparenting in Pipelines makes a mess)
in reality post Compare and Deploy any pull request creating in our instance would all go into our UAT branch, so the ablity to filter this would save time and mistakes.
A similar feature for branch creation would be great too.
This would probably need some user group filtering, as this wouldnt apply to all users
Chris Lewis
shared this idea
-
Ульяна Шинина commented
Useful feature. It's nice when production thinks about users. Melbet https://melbet-malbet.com/ provides a lot of interesting services, come in for sure!
-
Kyle Varga
commented
Agreed. We always want users making PR to a feature branch created from env/production but pointed to env/qa. Would love to block out the ability for users to manually be able to do anything different.