After doing some research to see if anyone else wanted the same thing that I wanted. I found SRCTREEWIN-782 on Jira for SourceTree. It says that it has not been started yet and I was wondering if this is something that will be done in the future or if it is not practical. I am fairly new to Git and SourceTree, but I understand how Git Flow works. I noticed that you already have the "Delete Branch" AND "Push changes to remote" on the finish process of "Release" portions of Git Flow and it merges and deletes the remote and local release branch. I was wondering if you could have the same "Push changes to remote" option for when finishing a "Feature". Currently it just deletes the local feature branch and leaves the remote feature branch there. Throughout time, this would create many, many, many feature branches in our Repository that we wouldn't use ever again. I personally feel like it "should" have the option to delete the remote feature branch.
+1 for this. It's very confusing after a while to tell which remote branches are still live. And my devs keep forgetting to delete them manually.
Agreed. I'd love to have a couple options: 1. delete from local; 2. delete from local and remote;
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.
I would like to see this feature as well
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 for this uption! this is what makes git flow so clear imo, it is so essential.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Totally agree. There should be an option in the dialog to delete the remote branch too... If forgotten, the origin/remote becomes soon a mess.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I too came across this issue. I found this fork of git-flow called the avh edition(https://github.com/petervanderdoes/gitflow) fixes this behaviour among other improvements. Its actively maintained unlike the original. There are feature requests to integrate the avh version to sourcetree. Please vote for them. (Windows - https://jira.atlassian.com/browse/SRCTREEWIN-1394, Mac - https://jira.atlassian.com/browse/SRCTREE-1762)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, totally agree (but I logged that Jira issue in the first place, so I'm biased :))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.