Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

ability to delete/remove release/hotfix/features easily #47

Open
tianon opened this Issue Aug 26, 2010 · 46 comments

Comments

Projects
None yet

tianon commented Aug 26, 2010

It would be great to have the ability to do something like git flow release delete v1.0.2, instead of git checkout develop && git branch -D release/v1.0.2 (which I'm not even sure correctly discards a release branch) and hoping no important steps were missed.

Owner

nvie commented Aug 26, 2010

That would be a good extra command.

PS: It is indeed the correct way to delete a branch. (Remember, git-flow doesn't do any hidden magic, it's just an implementation of the rules from the original blog post!)

Owner

nvie commented Aug 26, 2010

I would propose the following. If it is merged already in develop/master, but the branch pointer remains:

git flow release delete 1.0.2

To delete branched that are yet unmerged with develop/master (in order to avoid accidental deletion):

git flow release delete -f 1.0.2

tianon commented Aug 26, 2010

Ah, indeed. I would be quite happy with that functionality of the feature.

I was unsure about that being the correct procedure because it seemed like when I tried it, the commits I'd made to the deleted branch got merged into develop anyways, which really annoyed me, but I managed to take care of it and move along. Just to be clear, this would/should completely remove the entire branch and all its commits, given the -f flag, correct?

Owner

nvie commented Aug 26, 2010

Strictly speaking, it removes the branch object, which points to a commit (which points to a commit, which points to a commit, etc.). As long as you have any other branches pointing at one of those commits (like origin/feature/foo maybe), the commits will stick around. Otherwise, they'll be garbage collected eventually. That's just Git behaviour.

tianon commented Aug 26, 2010

Hmm, oh well. I must have screwed something up. Thanks for explaining, though!

dngreene commented Dec 6, 2011

+1 this feature. I'm trying to use git-flow to use the release candidates as our sprint deliverables, to be pushed to the testing environment, while maintaining master as the production codebase. In other words, in our environment, most release candidates will NOT be getting 'finished' to go to master - but all should be able to... so once a production release has been identified, I'd like to end the other release branches...

kwerle commented May 8, 2012

+1

@ghost

ghost commented May 10, 2012

+1

nexeck commented May 10, 2012

+1

+1 and I decided to implement this on my fork, currently only in the develop branch. Also added the ability to remove the remote branch as well.

atian25 commented Oct 26, 2012

+1 for this, is this feature supported now?

+1

Used this thread to figure out how to do it but would prefer built in method

It's been 2 years now... any chance it will get done? It's a good feature, I think.

+1

nzajt commented Nov 16, 2012

+1

Hello, it's already available in Peter van der Does fork with several other improvements.

+1

dbaba commented Jan 16, 2013

+1

mcplusa commented Jan 28, 2013

+1

+1

mborho commented Feb 5, 2013

+1

armanm commented Mar 17, 2013

+1

+4 (myself and my team @ work)! ^_^

Frully commented Mar 26, 2013

+1

Sangoku commented Mar 28, 2013

+2

rhacker commented Apr 10, 2013

@nrvs lolz :D
👍

tullo commented Apr 13, 2013

👍

+1

wmayner commented Nov 20, 2013

+1

yeco commented Nov 30, 2013

+1

occasl commented Jun 3, 2014

+1

ipimpat commented May 7, 2015

+1

ethzero commented Jun 9, 2015

+1

tchemit commented Jun 9, 2015

This is implemented in avh edition.

+100500

+100501

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment