You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
"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"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe the Sync Now button should correctly sync from the target branch of the PR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Im afraid this option cannot be disable. However, the pull request can be edited to fix the target branch if it was created incorrectly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm running into another issue with the Sync now button.
I have a pipeline setup to run on commits to feature/*
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.