-
Suggestion
-
Resolution: Unresolved
Our repo owners would like to ensure that active branches are deleted as soon as their pull requests are merged. At this time, the user creating the pull request can check the Delete on Merge box, but there's no way to guarantee that it's done.
It would be extremely helpful to have the ability for a repo admin to be able to set this at the repo level, rather than relying on users to do it on each pull request.
Latest update from Atlassian 2024-10-21
Bitbucket Cloud has started work on an option in repo settings (and project settings) that controls the default for "delete source branch after the PR is merged". We'll post an update here when the feature is available.
- is related to
-
- In Progress
[BCLOUD-21280] Provide ability to set default value for Delete on Merge at repo level
Hi all 👋 As mentioned on related suggestion BCLOUD-15300, Bitbucket Cloud has started work on an option in repo settings (and project settings) that controls the default for "delete source branch after the PR is merged". We'll post an update here when the feature is available.
Hi,
I see the ticket was created in 2021, if no one cares about it, just close it. Otherwise, it creates false hope!!!
Gotta be honest, this seems like a pretty basic function and I was as surprised as anyone to find out it didn't exist.
Can't believe this is not already the case... the current behavior is so missleading omg...
This feature was implemented in Bitbucket Server last year in https://jira.atlassian.com/browse/BSERV-12504
Isn't it the same codebase?
Is there any news of the progress ?
We're waiting for this feature to be enabled in Cloud product.
Having large numbers of open branches does impact jenkins pipeline performance so this feature would be very useful. I believe it has already made it into on-premise Bitbucket editions. It would be great to see it in the cloud product.
To add to this, we still want the option to deselect that checkbox, we would just like the default to be set to selected when creating a pull request
dparrish Wow - I had created this issue in 2017 and was removed as a dup and have been following this since. FINALLY!!!! Only took 7 years but better late than never... and never understood why this wasn't done to reduce repo space and keep it clean. A huge thank you for finally starting. Not sure to laugh or cry!!