In my team of 3, I want to ensure a PR can't be merged unless I have reviewed it.
To do this, in branch permissions, I selected:
And I set myself as the only default reviewer.
Works great, I am the gatekeeper for other people's PRs, except that when it is my own PR, my approval doesn't count, so I can't merge it.
I feel like I'm missing something. Is there any way around this?
Yep this is REALLY REALLY annoying, I currently turn off the merge check prevention, merge it, and turn it back on after. Because merging can take some time, you might have to waste your time waiting as well before you can switch it back.
Sometimes I get one of my devs to create the PR for me. It's still a nuisance.
Basically, Atlassian seems to have thought "oh, a PR author implicitly approves their own changes, so we can turn their ability to approve off" and then didn't consider the default reviewer merge check case AT ALL.
Yes, this is very annoying. As a default reviewer, it also doesn't allow merge if I approve my own PR.
I would expect the "approval from default reviewers" check should be ignored if you are yourself a default reviewer, especially if you are the ONLY default reviewer.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
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