Be git-describe friendly about gitflow HOT 11 CLOSED

@nvie, what about updating the graph tree on your blog with something like this?

from gitflow.

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

from gitflow.

Are there any plans to fix this?

from gitflow.

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

from gitflow.

I would support this change too

from gitflow.

+1

from gitflow.

+1 We too use git describe for the version identifier on our development versions.

from gitflow.

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

from gitflow.

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.

from gitflow.

can someone tell me what a good workaround would be for making git describe work?

from gitflow.

@tofutim use latest version of git-flow-avh which does back-merging of master into develop by default

from gitflow.