Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port "release" #3

Open
xsawyerx opened this issue Nov 16, 2010 · 2 comments
Open

Port "release" #3

xsawyerx opened this issue Nov 16, 2010 · 2 comments
Labels

Comments

@xsawyerx
Copy link
Owner

No description provided.

@dougwilson
Copy link
Collaborator

I wanted to put a note on this: some people are talking in gitflux about how the current git flow release branching model does not work with git describe. When you are on the development branch, say, and run git describe will the entire history being made from git flow, then you'll see

fatal: No tags can describe '...'.
Try --always, or create some tags.

This is because all the tags are on master and master is never merged into any other branches, so git describe will only work on master, which is not very useful. Essentially they are arguing that the model should be changed so that on git flow release finish it will merge the release branch into master, and then instead of merging the release branch into develop, merge the master branch into develop.

@dougwilson
Copy link
Collaborator

A user actually just submitted this as a bug in gitflow: nvie/gitflow#126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants