We follow git-flow branching model and also do code review. We use PR's and branch permissions to make sure no change is pushed into develop and release/* branches without being reviewed.
"Prevent All Changes Without a Pull Request" branch permission does not check initial push of a branch. For instance, a developer can create release/v1.1 locally. Than makes some changes locally (merge of another branch for example) and pushes it to the Bitbucket. Since the branch is new for Bitbucket Server, it does not check whether there is a new commit in the branch or not. As a result, a feature branch is included without being reviewed. I expect Bitbucket to enforce branch-permission rules in this scenario too.
In summary, "Prevent All Changes Without a Pull Request" does work for permanent branches like master or develop but has a flaw for "new" branches.
My question is how can we prevent the push of a modified new branch?
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events