Repository navigation
feat(claims): read claims and readiness from the upstream tree #192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
This file was deleted.
Oops, something went wrong.
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a remote fetches from GitHub but has an explicit push URL on GitLab, a local server, or another non-GitHub forge, this fallback incorrectly identifies the fetched GitHub repository as the head repository. Consequently
held()never checks branches at the actual push target, andquest startpushes there before trying to open a GitHub PR whose head branch does not exist on GitHub; the PR request fails and cleanup deletes the just-pushed branch. Preserve the GitHub repository for upstream-tree reads, but represent the non-GitHub push target separately so it is checked as a branch-only source and no PR is attempted.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving this as is for now. Before this PR, the head was always the fetched repository whatever the push URL said, so the fallback keeps the old behavior for that setup instead of adding a third mode. It also fails loudly: GitHub refuses to open the PR, the just-pushed claim branch is deleted with its lease, and
quest startexits 1. A GitHub fetch URL with a non-GitHub push URL (a mirror, say) is rare, and making it a branch-only claim source would need its own design, for example whetherunblocked --unclaimedshould check branches on two forges. I listed it as a suggested follow-up in the report.(Written by Claude Opus 5.5)