feat(git): support commit-set in /ensure-refs#305
Merged
Conversation
EnsureRefs previously only accepted a refs map and required keys to be ref names. To pre-warm individual commits (e.g. a PR head SHA that may not yet point at any named ref), callers had to construct a fake ref. Extend the request to accept an explicit commits list.
The endpoint now accepts {"refs":..., "commits":[...]}, with at least one populated. The server fetches once if any ref is wrong or any commit is missing from the local object database, then reports resolved ref SHAs and any commits still missing after the fetch.
The client API takes an EnsureGitRefsRequest struct so the field set can grow without further breaking changes. cachew git restore gains a --commit flag (repeatable) and treats the local short-circuit symmetrically across refs and commits; a server response with missing_commits is fatal.
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.
EnsureRefs previously only accepted a refs map and required keys to be ref names. To pre-warm individual commits (e.g. a PR head SHA that may not yet point at any named ref), callers had to construct a fake ref. Extend the request to accept an explicit commits list.
The endpoint now accepts {"refs":..., "commits":[...]}, with at least one populated. The server fetches once if any ref is wrong or any commit is missing from the local object database, then reports resolved ref SHAs and any commits still missing after the fetch.
The client API takes an EnsureGitRefsRequest struct so the field set can grow without further breaking changes. cachew git restore gains a --commit flag (repeatable) and treats the local short-circuit symmetrically across refs and commits; a server response with missing_commits is fatal.