Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,551,765
Community Members
 
Community Events
184
Community Groups

PR in BitBucket not updated with new commit

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.

1 answer

0 votes
Tyler T
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 20, 2020

Hello and welcome to the Community!

Are you using Bitbucket Cloud or Bitbucket Server?

Bitbucket Server

Tyler T
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 21, 2020

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 ?

Tyler T
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 24, 2020

Are any of those options set? The rewriting history setting could be affecting your force-push issue.

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.
image.png

Tyler T
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 03, 2020 • edited

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/#/

I'm having this issue and I was told to ask the community.

Like David Kind likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events