Add sha256 checksum output to the formatting options #2974
Merged
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
isaacsu
reviewed
Sep 6, 2024
isaacsu
reviewed
Sep 6, 2024
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.
Description
When running
artifact shasumyou can optionally print the SHA256 checksum for a single artifact.But if you're trying to list multiple artifacts using the
searchsubcommand, we only support printing the SHA1 checksumChanges
Add new formatting option,
%T, for SHA256. I chose t because it's the next letter in the alphabet and both%sand%Sare taken. Open to suggestions!Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go fmt ./...)