Track upstream branch in update examples #231
Merged
Conversation
This file contains 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
This allows the `gh` CLI to know which remote branch to use for PRs
jhkennedy
force-pushed
the
gh-cli-debug
branch
from
29b0bb3 to
908563c
Compare
jhkennedy
changed the title
jhkennedy
changed the title
jhkennedy
force-pushed
the
gh-cli-debug
branch
from
dfb047d to
908563c
Compare
jtherrmann
approved these changes
Jan 17, 2025
jtherrmann
added
the
bumpless
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.
The update examples action fails because
gh prdoesn't know which remote branch to use. Simply tracking the upstream branch when we push the proposed changes is sufficient forgh pr, or, we could explicitly set--head origin/BRANCH_NAME. I prefer the former.You can see a successful run of the Update Examples action in #233 which was created from this PR (908563c, specifically).
fixes #229