Feature request to look up most recent tag used in the current repo before starting release or hotfix about gitflow.vs HOT 6 OPEN

You would still type in one manually as in today, but at the moment you type it in, you could see the most recent tag applied (ie: "Last tag: 1.3.1"). It would either determine the last tag by timestamp of the tag or natural ordering of the version (1.10 would be considered more recent that 1.9 - most apps we have used, like source tree, are unable to do natural ordering of subversions).

The reasoning of the above is that we have adopted semantic versioning for our releases (as was essentially described by Vincent Driessen). Therefore, iif our last tag was "1.2.1", then our next release or hotfix will either be "1.2.2", "1.3", or "2.0". We just need to know the last tag was "1.2.1" so we can determine which of the 3 options we would choose. It would be slick to allow the manual entry of the version, but a combo-style box where it would suggest one of those 3 versions based on my last tag.

from gitflow.vs.

That's a great idea. So, it would let you select a tag from the most recent ones, or let you type in one manually (as today)?

from gitflow.vs.

I'm working on support for the AVH support and bugfix branches in my branch, and might soon be able to provide a pull request from mine.
In there i also made a function that finds tags on a branch (hardcoded now to master) to start a supportbranch from a certain release (tag)
This might help with this hotfix or release from tag issue?

As this is the first project i started collab on, i'm not really familiar with guidelines etc for this kind of work, so i apologize beforehand if i step on any toes!

from gitflow.vs.

+1 for this very good idea!

from gitflow.vs.

That sounds great! It would be nice if these two functionalities could be separated into two different pull requests, to make it easier to merge them separately. But if that creates a lot of work, please just send a PR for the entire change and I'll take a look at it.

Thanks!

from gitflow.vs.

The support and bugfix addition is a bit intertwined as they both more or less affect the same files.
But the actual start/finish UI for support/bugfix aint started yet, only the init part is done so far, so i can separate it when i work more on it

We switched to GIT from svn at work, and had a 2 day course about it as well.
And when looking around i stumbled upon git flow, and subsequently this project.
So thank you!

PS. Would be really nice to get a "grapher" to be able to pick commits on the tree, for starting branches by right click or something! :)

from gitflow.vs.