Add --version flag and embed build-time version metadata #3
Conversation
This file contains hidden or 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
takai
changed the title
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.
This pull request adds explicit version reporting to the CLI and ensures version metadata is embedded at build time.
A new
--versionflag has been introduced to display the application version together with the corresponding Git commit hash. This allows users to quickly verify which build ofgit-ai-committhey are running, which is particularly useful when troubleshooting issues or comparing behavior across releases.To support this, the build process has been updated to inject version and commit information at build time using Go linker flags. The GoReleaser configuration now passes the release version and short commit hash into the binary, replacing the previous hardcoded defaults used during local development.