Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

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

Open
tianon opened this Issue · 42 comments
@tianon

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.

@nvie
Owner

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!)

@nvie
Owner

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

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?

@nvie
Owner

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

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

@dngreene

+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

+1

@ghost

+1

@nexeck

+1

@petervanderdoes

+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

+1 for this, is this feature supported now?

@DArrigoni

+1

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

@netcriptus

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

@nzajt

+1

@baby-gnu

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

@dbaba

+1

@mcplusa

+1

@mborho

+1

@armanm

+1

@nrvs

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

@Frully

+1

@Sangoku

+2

@rhacker

@nrvs lolz :D
:+1:

@wmayner

+1

@yeco

+1

@occasl

+1

@kimse1

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.