When you create a pull request in Bitbucket you can select the option to "Close Branch" or if you did not select that option when it was created when it is merged you can chose to "Close" it at that time too.
However, by selecting to close the branch does absolutely nothing to the branch in any interface except for Bitbucket. So I am not going to ask Atlassian why they do not delete the branch. What I want to know is, what is the benefit, to me the end user/customer, does this purposeful design option provide? Because all I can see is that, it just clutters up the branch lists in SourceTree and cause me to do additional "work" that, frankly, I do not understand why I should be doing it anyway.
Because Bitbucket does not delete the branch, what is the suggested method for deleting these branches and how long should they be kept? I assume that you have a automated process for "cleaning" up these after the assigned duration that they should be kept. So if you would please provide a link to that documentation, that would be great!
Hi @Dale Cook,
However, by selecting to close the branch does absolutely nothing to the branch in any interface except for Bitbucket.
You are right, closing a branch in Bitbucket does not delete it from your local repository. It does, however, delete it from the remote repository on bitbucket.org.
The branches you see in SourceTree are most likely branches on your local repository. Bitbucket does not (and should not) have access to your local repository, which is why the branches are still present there. As @Tom Roche mentioned, this is typical behaviour for a DVCS such as git.
It's a good practice to clean up/close branches on the remote if they are no longer needed for a few reasons:
You are free to delete the branch from your local repository any time you like, either using SourceTree or the command line.
There are various scripts which will find merged branches and delete them from your local repository, I suggest you look those up if you have quite a few old branches in your local repository.
For more information on using git and best practices, you can check out the Atlassian 'Getting Git Right' site.
I hope that helps,
I do not want to sound dumb but the branch is not deleted from Bitbucket.org. If you get a complete list of the branches from origin, the branch will still be there. You can even checkout the branch again, because I have done it. (I just did it again to make sure I was not wrong.)
I have just tested this and for me the branch is definitely deleted from bitbucket.org. Note that even if you're listing remote branches in your local repository, git will show you the local tracking branch for the remote branch.
So again, it is in your local repository. If you do not see the branch in Bitbucket's branch list, it has been deleted on the remote.
git remote prune as @shabbaranks suggests will remove the tracking branch from your local repository as well.
@Dale Cook: 'selecting to close the branch does absolutely nothing to the branch in any interface except for Bitbucket.'
I don't work for Atlassian, and don't use SourceTree, but I have used `git` and other distributed version control systems (DVCS) for awhile. ISTM this is working as designed, and that you need to learn about how DVCS work, particularly the differences between distributed and centralized version control.
@Dale Cook: 'Because Bitbucket does not delete the branch, what is the suggested method for deleting these branches'
Again, I don't know how one does this in SourceTree, but in good old-fashioned command-line `git` (or in the awesome Emacs package=`magit`) one would
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs