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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
If you do a forced push of a branch which has a PR the PR isn't updated. The branch view shows the new commit but in the PR no change is visible. If you decline and re-open the PR the change is visible.
Hello and welcome to the Community!
Are you using Bitbucket Cloud or Bitbucket Server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have any branch permissions setup that might be preventing a force-push?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The branch permissions consists of these 3 options :
1)Rewriting history
2)Deletion
3)Changes without a pull request
Do I need to change any setting ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are any of those options set? The rewriting history setting could be affecting your force-push issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I deleted the 'Rewiritng History' option from the Branch permissions but It is also present in the Project settings .
And the user noted that the problem wasn't on master and this is needed for the Admins.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, using the Prevent -> Rewriting history setting probably something you want to keep set on master. Your original issue was the the pull request didn't update in your feature branch.
If you are still having an issue I recommend you open a bug report with the support team so they can investigate this further: https://support.atlassian.com/contact/#/
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.