Set up versioning from git tags using mill #225
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a version number to BASIL's help text based on
git describe --tags
. It shouldn't cause issues when git isn't available, falling back to whatever is in the VERSION file. The VERSION file stores the version number of the last tagged release.git describe --tags
if git is available at build-time, or the contents of the VERSION file if not.The Scala version file is generated each build is not checked in.
This means the process for making a release is
git tag -a "$(cat VERSION)"
Alternatively, just adding a git tag will bump the version file on the next build, which will mean the the tagged commit has the old version file, but builds with the correct version when git is present.