Repository navigation
ci: set origin/HEAD before running release.sh - #168
Merged
Merged
Conversation
actions/checkout does not create refs/remotes/origin/HEAD, so release.sh's default_branch() resolves to an empty string in CI, as the first sdk-python Cut Release run showed.
eddietejeda
requested review from
shefeek-jinnah
and removed request for
a team
October 15, 2026 19:38
eddietejeda
enabled auto-merge (squash)
October 15, 2026 19:38
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.
Same fix as sdk-python: the first Cut Release run there failed in
release.sh preparewithfatal: empty string is not a valid pathspecbecause the script resolves the base branch fromorigin/HEAD, whichactions/checkoutnever sets. Both jobs now rungit remote set-head origin --autobefore calling the script. No script change.