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

[Ben Tillman]

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.

[Alex Anderson]

"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"

[Alex Anderson]

(JIRA issue for changing Sync Now to rebase: https://jira.atlassian.com/browse/BCLOUD-6202)

[Eric Berndt]

i too vote for the "disable" or "rebase" options

[Lenin Raj]

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

[Ben Tillman]

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.

[Lenin Raj]

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

[Rob Benton]

Can this not be prevented using some sort of branch restriction? We use a gitflow model and we don't want people accidentally hitting "sync now" to merge dev into master which would ruin our production code.

[Jim Priest]

I'm running into another issue with the Sync now button.  

I have a pipeline setup to run on commits to feature/*

1. I push my feature branch up - the pipeline fires and my feature branch is deployed to QA
2. I create a pull request to merge my feature branch into develop
3. Within the pull request Bitbucket informs me my branch is behind and I can sync now 
4. If I click Sync Now it merged Develop > Feature - which fires my Pipeline again!
   
   
   

[Ben Tillman]

I believe this is by design. Since clicking Sync Now will make a merge commit from develop into your feature branch of all the latest changes on develop not contained in your feature branch. This commit is then what is triggering your pipeline.