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: * "Check for at least 1 approval" * "Check for at least 1 approval from default reviewers" * "Prevent a merge with unresolved merge checks" 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?

2025, and it is still there. I cannot approve my own PR, even though I am the only default reviewer in my team. That is insane!

Logically it doesn't make sense that: - You, the default reviewer, write some code and another non-default reviewer dev approves it. You cannot merge the code. - The other dev writes some code, you approve and can then merge the code. The same two people are involved.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Only default reviewer can't merge own PR when approval required from at least 1 default reviewer

catapult-sam

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:

"Check for at least 1 approval"
"Check for at least 1 approval from default reviewers"
"Prevent a merge with unresolved merge checks"

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?

Accepted answers

All comments

Kevin Danikowski

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.

Max DeCurtins

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.

Jason Sheedy

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.

rohan_martin

Wow, this absurd restriction is still in place.

I am the only full-time technical person at a startup, with contractors coming and going. I do not want to remove the merge check to prevent any contractor from merging a PR without my approval, but the majority of the time I am the only developer. I can't merge a PR even though it has been approved by 100% of the development team (ie. me).

I don't see temporarily disabling the merge prevention as an option, as I don't know when contractors will be performing reviews.

I have had to create another account for myself and use that for approving PRs, but that takes up a space in our team count.

Antonio Lopes_2iqb5s

Mar 2020 - May 2023.

Ridiculous.

Daniel Ambler

+1 - thought I'd found the perfect way to control my documentation only to have my hopes dashed at the last hurdle.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud