Repository navigation
feat(server): a fork's PR list follows the gh default repository - #30
Merged
Merged
Conversation
A checkout with both `upstream` and `origin` always took `upstream` as its repository, so a fork's PR view listed upstream's pull requests and none of its own. The resolver now prefers the remote `gh repo set-default` marked (`remote.<name>.gh-resolved base`), then `upstream`, then `origin`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
A checkout with both
upstreamandoriginremotes always tookupstreamas its repository. In this fork that pointed the PR view (web, desktop and Android) at upstream's pull requests, and the fork's own PRs never appeared.The repository identity resolver now prefers the remote that
gh repo set-defaultchose (git configremote.<name>.gh-resolved base), thenupstream, thenoriginas before. Checkouts without a gh default behave as they did. It reads the config in parallel withgit remote -v, once per identity cache miss.Runtime check against a fork checkout after
gh repo set-default tebiggs/t3code:The sidebar's grouping key and display name don't change, because they already preferred the fork's
origin.Done by Claude Opus 5.5 in Claude Code (T3 Code).
🤖 Generated with Claude Code