ability to delete/remove release/hotfix/features easily about gitflow HOT 61 OPEN

You can now use git flow <thing> delete <nameOfTheThing>

from gitflow.

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

from gitflow.

please, stop commenting just "+1", it's 2020 and Github already introduced emojis for this purpose 👍

from gitflow.

Wow, can't believe this is still a thing. It's been almost 8 years waiting for this command.

from gitflow.

@geoom

+1

from gitflow.

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

from gitflow.

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?

from gitflow.

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.

from gitflow.

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

from gitflow.

+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...

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+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.

from gitflow.

+1 for this, is this feature supported now?

from gitflow.

+1

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

from gitflow.

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

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

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

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

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

from gitflow.

+1

from gitflow.

+2

from gitflow.

@nrvs lolz :D
👍

from gitflow.

+1

from gitflow.

👍

from gitflow.

+1

from gitflow.

👍

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

This is implemented in avh edition.

from gitflow.

+100500

from gitflow.

+100501

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

+1

from gitflow.

wow, after nine years, this is still a thing
really need this feature

from gitflow.

This is implemented in https://github.com/petervanderdoes/gitflow-avh It's backwards compatible with this version but adds many improvements and new features.

Disclaimer: I'm the project lead for Gitflow AVH Edition

from gitflow.

+1

from gitflow.