actions/checkout: manually fetch ci/pinned.json patch#482470
Merged
MattSturgeon merged 1 commit intoJan 22, 2026
Conversation
5dcda20 to
99117d5
Compare
This was referenced Jan 22, 2026
Merged
philiptaron
approved these changes
Jan 22, 2026
In a shallow clone, `git fetch` may fail to apply thin packs due to missing base objects. We typically don't notice this with first-parent commits and prospective merge commits, but it seems fairly common with arbitrary PR-branch commits. In this instance we don't need the full commit data, we only need to apply its diff as a patch. So fetch the diff from GitHub's API and apply using `git apply`. This partially reverts commit 4787f35
MattSturgeon
commented
Jan 22, 2026
99117d5 to
79f6bf1
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Contributor
|
Successfully created backport PR for |
1 task
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
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.
#480395 does not seem to be enough to resolve CI issues for #480141, yet. Despite testing #480395 thoroughly, it seems that in #480141 we run into issues with shallow clones, thin fetch-packs, and missing base objects:
In a shallow clone,
git fetchmay fail to apply thin packs due to missing base objects.We typically don't notice this with first-parent commits and prospective merge commits, but it seems fairly common with arbitrary PR-branch commits.
In this instance we don't need the full commit data, we only need to apply its diff as a patch. So fetch the diff from GitHub's API and apply using
git apply.This partially reverts commit 4787f35 from #480395
Things done