Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Merge check changes not taking effect

I had merge check minimum approvals set to 2 at the project level, and inherited to all repositories. I changed minimum approvals to 1, but the new merge checks are still requiring 2 approvals. I then set the repository in question to enable (not inherited) and set that to only require 1 approval. It still does not honor it, and requires 2.

I know that the pull requests made prior to that change will still require 2, but even the new ones are not honoring the change to the merge check. Is this a known bug, or what else might I be missing?

0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events