buildcommands: Add support for a versionstamp file #6742
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If a file is located at src/.version, and git cannot determine the current version, the contents of this file is used as the version. This is equivelant to similar behavior in klippy. Signed-off-by: Aaron Haun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds support for a versionstamp file at src/.version, similar to the one used by klippy at klippy/.version.
If git cannot determine the version being built (either because git is not present on the system, or klipper was downloaded as a tar/zip from github) buildcommands will read src/.version as a fallback. Versions determined this way are always considered "clean".