Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I disable "Sync Now" on Branches/Pull Requests in Bitbucket Cloud? Edited

While some find the "Sync Now" feature useful for keeping a pull request or a branch up to date, we want to have our developers learn the ins and outs of Git by having to do this themselves manually, so I wanted to see if there was any thought on having this feature be controlled by an option per repository?

In addition to wanting our developers to learn more of the ins and outs of Git by not having this, we have also run into issues where it is erroneously clicked on when a user views a feature branch and Bitbucket shows the incorrect destination branch (when we have two mainline branches), so the feature branch ends up getting synced with the wrong destination branch.

2 answers

"Sync now" is also unhelpful for teams/repos using squash/rebase workflows, as it makes rebasing onto the target branch more complicated.

It would be very helpful to:

* have an option to disable "Sync Now" or
* have an option to change its behaviour to rebase, or
* change its behaviour to rebase if the repo's Merge Strategy is set to "squash"

(JIRA issue for changing Sync Now to rebase:

Like # people like this

I believe the Sync Now button should correctly sync from the target branch of the PR

You are correct that the Sync Now button will sync from the target branch of the PR, but if the user were to pick the wrong target branch and then click Sync Now, it would then become out of sync. I am simply looking for a way to disable the Sync Now button per repository since we are trying to have people on our team learn the ins and outs of Git Flow, which would mean keeping the branch in sync not via the Sync Now button in the Bitbucket UI.

Like # people like this

Im afraid this option cannot be disable. However, the pull request can be edited to fix the target branch if it was created incorrectly.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

338 views 2 10
Read article

Community Events

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

Events near you