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

Delete source branch after merging by DEFAULT


Any way/add-on/workaround to tick the 'Delete source branch after merging' by default on every merge window?



2 answers

For Bitbucket Server you can set this up on a project-level under Settings > Branches (under the Workflow section), scroll to the bottom and change the default 'Branch deletion on merge' setting on and press save



Does anybody now if that option is available or will be implemented for Bitbucket Cloud? Couldn't find it there with my not premium account.

Like # people like this
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Jan 31, 2023

Our development team was concerned about this in Bitbucket Cloud, so I developed a Chrome extension that automatically checks the checkbox for deleting the branch when merging.

It is Open-Source, and you can download it from the Chrome Web Store.

0 votes
Anton Genkin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 23, 2020

@Daniel Juravski there is no global setting that changes the default state of this checkbox. The state of the checkbox is saved per user/repository. For example, if you choose to delete branch after merge in repository ABC, on next merge the checkbox will be checked.

If you still need to have this checkbox checked by default, here are a few options:

  1. Try JS script - 
  2. Use a script for ScriptRunner for Bitbucket - Link
  3. Automate deletion of merged branches using CI


If you could tell us more about your use-case that would be great - BSERV-9254

I would appreciate having it checked by default because I often forget to check it. Our teams tend to forget it as well and this has lead to use having a lot of dead branches that we have to clean up. They're not that hard to clean up, but they really pile up. This would be much easier if the box was checked by default. Thank you!

Like # people like this

This is misleading. The "default" only is a default as long as the user never has merged in that repository.

I would expect a default to be the default on each subsequent merge. The state should not be remembered.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events