Tag vs commit ordering - Githubissues

c4urself / bump2version

Version-bump your software with a single command

https://pypi.python.org/pypi/bump2version

MIT License

1.05k stars 134 forks source link

Tag vs commit ordering #194

Open tfcollins opened 3 years ago

tfcollins commented 3 years ago

Is there a way to change the ordering between tagging and adding the bump commit?

For tagging, I add tags to the last commit before bumping the version in source. That way it's easy to differentiate between a release and development.

florisla commented 3 years ago

No, I don't think that's possible.

Do you have an example of this workflow? It sounds like you have multiple commits in the repository with a non-development version string?

tfcollins commented 3 years ago

I actually have an invoke task for this but would like to move to b2v: https://github.com/analogdevicesinc/pyadi-iio/blob/master/tasks.py#L94

-Travis

florisla commented 3 years ago

Thanks,

So the use case is:

Have version string 0.0.7 in master while 0.0.7 is in development.
Tag it as v0.0.7 when it's ready.
Immediately bump to 0.0.8 after tagging.

@tfcollins Is there any particular reason you don't want to use a -dev suffix while in development? That would allow you to distinguish a released/tagged version from an in-development one. E.g. to detect if users are using the master branch with non-released functionality.

tfcollins commented 3 years ago

I would say this is more out of habit from other projects I've worked on. I tend to avoid using tags unless to mark releases. For development there can be a few branches that are in play so having a single tagged dev doesn't totally fit.

-Travis