AutoMerge and RegistryCI: Add support for commit hash information #537
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
simonbyrne
force-pushed
the
sb/commit-hash
branch
2 times, most recently
from
74d78fa to
aefcf2d
Compare
simonbyrne
force-pushed
the
sb/commit-hash
branch
from
aefcf2d to
cfe54df
Compare
DilumAluthge
reviewed
Jan 2, 2024
Member
|
just to say #609 is a bit related; there we laboriously extract commit SHAs from old version's tree SHAs out of the package's git repo. If the commit sha was in the registry we could skip that. |
DilumAluthge
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Part of JuliaLang/Pkg.jl#3718.
This does not depend on any other changes, but the keys should match those in JuliaRegistries/RegistryTools.jl#97