docs: gh pr update-branch --rebase + BEHIND detection in PR workflow#79
Merged
Conversation
Document remote-rebasing a conflict-free PR onto its base without a local clone (no merge commit, rebase-only compatible), and that mergeStateStatus only reports BEHIND when the base enforces up-to-date branches — otherwise use the compare API's behind_by to judge staleness. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
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.
Adds two field-tested PR-maintenance notes to
references/pull-request-workflow.md(Conflict Resolution section).gh pr update-branch <n> --rebase— remote-rebase a conflict-free PR onto its base with no local clone and no merge commit (rebase-only compatible). Only succeeds whenmergeable: MERGEABLE; force-updates the branch (re-triggers CI, can reset approvals), so reserve it for PRs staleness actually blocks. Handy for a bulk 'rebase all my open PRs' sweep.Judging 'behind' correctly — GitHub only reports
mergeStateStatus: BEHINDwhen the base enforces 'require branches up to date'; otherwise a PR many commits behind still showsCLEAN/BLOCKED. Usegh api .../compare/<base>...<head> --jq .behind_byto know the real distance, and don't rebase conflict-free-but-behind PRs unless staleness blocks merge.Content-only append to an existing reference file already in the SKILL.md index. markdownlint clean.
🤖 Generated with Claude Code