Use case: pre-bump and tag last commit

[flyte]

On some projects, after assigning a new version to a release, the version number is bumped in the repository in preparation for the next release. In this case, the version tag should actually point to HEAD~1, or the commit before the one bamp just made. How could this be handled in bamp?

[inirudebwoy]

Unfortunately this is not possible with bamp. The tag is placed always on the commit created by bamp.
I don't know what to think about it as can't remember the situation I'd used it. Taking into consideration number of people releasing software I possibly can't be right on this ;)

Should the tag be always placed on HEAD~1? or should it be configurable?

[flyte]

I believe the process is something like the following:

• Do lots of commits on your project
• Decide that you want to make a release
• Do the release (push to PyPI or whatever) using the version number currently in the repo
• Tag the latest commit as that version number
• Add a new commit which bumps the version number
• Do lots more commits on your project
• Profit