Is it possible to set pull request settings on a branch instead of repo level? Example:
We allow teams to set pull-requests on all repos other than release/*. Release/* pull-requests are required. On every repo, we want release/* to require pull-requests to have a successful build. however, on develop/* or feature/*, or anything else, we don't care. There are teams that want to require pull-requests on multiple branches, as they're managing open projects, but do not want there to be a successful build every time (especially for small changes, like uprevving the component version in a POM).
If there's no way to set this now, is it on the roadmap? This would be supremely helpful for our workflow.
I have found this plugin:
https://marketplace.atlassian.com/plugins/com.mobikop.stash.MergeRestrictions/overview
Looks like it can set merge restrictions PER branch name/pattern etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try workzone for Bitbucket. It allows you to configure advanced merge restrictions on branch(pattern) level. Available for Bitbucket 4 and 5.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm confused about the wording. Are release/* , develop/* , feature/* repositories (and not branches)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ah, oops, just re-read your question and parsed it more successfully this time. No, I don't think you can do that currently.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.