As title. Setting per repo is enough. I would like to let all pull requests of this repo have this ticked. Our repo is hosted in Bitbucket Cloud. Thanks!
Hi @Zejia Chen ,
welcome to the Atlassian community!
Usually, this setup is per user basis. As a user, if you choose to delete branch after merge in repository, on next merge the checkbox will be checked.
Btw, there's an open request to make this setting as default per all users. You can vote and watch this request https://jira.atlassian.com/browse/BCLOUD-21661 in order to be updated.
Hope this helps,
Fabio
Hi @Fabio Racobaldo _Herzum_, could you elaborate on
Usually, this setup is per user basis. As a user, if you choose to delete branch after merge in repository, on next merge the checkbox will be checked.
I can't see this memory effect at PR creation time, whle at PR merge time I simply see the value previously set by the proposer on the PR.
(in the meantime I voted for the feature request you linked)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In Flowie, a Bitbucket cloud app for defining workflows that we provide, you can configure it to always, or depending on a condition, close the source branch, so developers don't even need to worry about this.
Flowie is available via the Atlassian Marketplace.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems that Bitbucket Server includes a setting to automatically delete the branch after merging, but is not included in Bitbucket Cloud.
This was a concern to our development team, so I developed an Open-Source extension for Google Chrome, which you can install from the Chrome Web Store.
I hope it helps!
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.