You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Using Bitbucket Server, I want to ensure that every change is reviewed by a different person before it can can be merged to the main branch.
Now, let's say, a colleague of mine opens a pull request in Bitbucket Server and assigns me as a reviewer. I then push a change to the pull request's branch and then I approve the pull request. This has successfully circumvented the original requirement that every change is reviewed by a different person.
Can I somehow prevent that?
that's a great question. It's a good idea to keep your pull request workflow clean so that your very clever developers can't cut corners :D
I don't think the 'ignore committer approvals' feature is available in Bitbucket server/dc.
We have built Workzone for Bitbucket enterprise teams that offers extensive reviewer and merge configurations.
On of the features is 'Ignore committer approvals' in Workzone's merge configuration . When Bitbucket+Workzone count pull request approvals for a merge-check (the verdict whether or not a PR can be merged or not) any reviewer who has also committed code to the PR source branch and is therefore part of the changeset authors will be ignored when counting approvals.
With this setting in place the effective approval count would be 0 in your use case.
I hope this helps, let us know if you need any further assistance solving your use case.