Show git commit on Console Status and in the release README #466 - #822
Open
AzazelSensei wants to merge 1 commit into
Open
Show git commit on Console Status and in the release README #466#822AzazelSensei wants to merge 1 commit into
AzazelSensei wants to merge 1 commit into
Conversation
System Status now lists the build hash as a git commit, /api/version.xml maps buildHash to that value, and the packed artifact gets README.txt with the same hash. Fixes yacy#466
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I put the build git hash on Console Status as its own Git commit line, and packed the same hash into README.txt in the release tarball so you can read it without starting YaCy.
/api/version.xmlbuildHashwas wired to the datetime placeholder; it now uses the hash.