#12809 Attempt fix for failing backport action - #12810
Merged
Merged
Conversation
tdipisa
approved these changes
Aug 17, 2026
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
2 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.
Description
The backport action reports
couldn't find remote ref <branch>on branches that do exist. The real error in the logs isfatal: shallow file has changed since we read it: the action runs its own shallow fetches on top of the shallow clone we check out, and they clash.Checking out the full history removes the shallow file.
filter: blob:nonekeeps the checkout fast.Fixes #12809
Test
Cannot be tested before merge:
pull_request_targetruns the workflow from the base branch. Once merged, re-apply thebackport 2026.02.xxlabel on #12557, which fails reproducibly today.