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

Ability to disable auto-updating pull requests

Our team is looking for a way to disable pull requests from being auto-updated whenever code is pushed to the branch in the request. We would prefer to let the issuer of the PR choose when to update the code in the PR. This would allow our developers to continue to regularly push code to the branch they are developing in without reviewers having their review status changed to "Unapproved". Reviewers should only have their review status changed to "Unapproved" once the developer has determined that the branch is ready to review again.

As far as I know, this is not currently possible in BitBucket cloud. I am open to suggestions about how we can modify our git workflow to facilitate this, but I do not want to have to create additional "staging" branches for every development branch.

There is an old Jira issue requesting this feature, but the issues seems to have been closed without careful consideration:

1 comment

Ulrich Kuhnhardt _IzymesCo_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Sep 10, 2022

Hi @Isaac Kroger 

welcome and thanks for sharing.

I guess your team has a pull request workflow that basically goes like this:

1. Here is a draft pull request everyone, please leave your comments, request changes or approve.

2. Thanks for your feedback everyone, I've made some changes, incorporated your comments and now the pull request is ready for real.

3. Everyone who hasn't approved in the first round, please approve now.

Is this the kind of workflow you need, a sort of multi-staged approval?

I'm asking because we're at Izymes try to understand all enterprise team SCM workflows and help out where we can.

Thanks and looking fwd to your thoughts, Ulrich


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events