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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

BitBucket change announcement: "Pull requests are now immutable" - what does this mean?

The Atlassian Change Blog provides details about new and pending changes being rolled out to customers of their products.

The BitBucket Cloud section of this week's blog (Jan 16 to Jan 23, 2023) linked above contains this cryptic new entry:


Text version:

Pull requests are now immutable
Bitbucket Cloud pull requests are now immutable. Note: You might come across pull requests that were merged before this change was implemented, so you may see some changes that are not relevant anymore.

Can anyone explain what this entry means and what functionality was actually changed?

I've played around with several test pull requests, but so far have not noticed any difference in capabilities or features.


1 answer

2 votes

Thanks for posting this question. I would love an explanation too.

I poked about a bit and what I think is different is that 

Merged pull requests are now immutable :=)

  •  you cant change the title or description
  • you can't Un-approve or approve post merge

Looks like you can still leave comments.

Like # people like this

@Ulrich Kuhnhardt _IzymesCo_ Thanks for your observations, I suspect you are correct.

I've also noticed that modifying or deleting the source branch of a merged PR no longer appears to alter the code diff displayed in the interface for that merged PR (an unintuitive display defect that I recall noticing in the past, although I cannot say with certainty when it changed because our team quickly learned to avoid that behavior).

It would be nice to get some clarity from Atlassian regarding whether we've correctly divined the extent of the recent changes.

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events