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.
Hi,
Any way/add-on/workaround to tick the 'Delete source branch after merging' by default on every merge window?
Thanks!
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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:
If you could tell us more about your use-case that would be great - BSERV-9254
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.