It's been mentioned in the original blog post's comments section, and on this thread: the current way releases are finished merge the release branch into master and develop, but does not record a relation between them, which makes git-describe output very inconvenient (if not to say very confusing :)).
For example: consider the case where you have a version 1.0 tagged, then finish a new 1.1 release. When using git-describe, it scans the commit tree upwards, and finds 1.0 as the first tagged commit, generating a misleading identifier somewhat like 1.0-52-g25def71, instead of something like 1.1-8-25def71.
This requires a change to the original branching model, too.
nvie
All 11 comments
I'm thinking of starting to use git-flow, but this issue makes me a bit hesitant. Have you made any progress on it?
Thanks :)
ghost
on 1 May 2011
Are there any plans to fix this?
michaelritsema
on 27 Jul 2011
+1
I just stumbled upon that issue on my new release workflow today and found this issue here on github. This should be fixed to make the tags more useful to these how want to use git describe as version identifier on development versions, too.
jk
on 5 Sep 2011
I would support this change too
dreamiurg
on 30 Sep 2011
+1
aseemk
on 2 Oct 2011
+1 We too use git describe for the version identifier on our development versions.
richardbuckle
on 18 Oct 2011
+1. Any progress on this? This issue has now been opened for over a year with no update, and pull request #85 which addresses this has been largely ignored since it was opened in Dec 2010.
putermancer
on 19 Oct 2011
I've looked at pull request #85 and it looks perfectly good. Given the announced decision to amend the branching model, I'm a bit disappointed that this pull request hasn't already been adopted.
richardbuckle
on 19 Oct 2011
can someone tell me what a good workaround would be for making git describe work?
tofutim
on 28 Mar 2018
@tofutim use latest version of git-flow-avh which does back-merging of master into develop by default
lcb
on 19 Apr 2018
@nvie, what about updating the graph tree on your blog with something like this?
vdsbenoit
on 19 Feb 2020
Related issues
alexjeffburke
·
24Comments
ripper234
·
9Comments
nvaken
·
5Comments
boryn
·
6Comments
harshadyeola
·
4Comments
Most helpful comment
@nvie, what about updating the graph tree on your blog with something like this?