Repository navigation
fix(pull-requests): scope project lists to the origin fork - #130
Merged
Merged
Conversation
Resolve project repository identity from origin before upstream. Keep the existing upstream and alphabetical fallbacks for checkouts without origin. Selected-project reads target that repository directly instead of making a host search before repeating the repository search for an unindexed fork. Reject saved GitHub rows whose repository no longer matches their project's current origin, including authored and reviewing priority groups. Keep environment identity in that comparison and leave other providers' server-side host refinement alone. The current GitHub account still comes from the existing verified credential lookup. Add focused resolver, authored-query, selected-project listing and carried-row regressions. Tests, typechecks, lint, formatting and GUI checks were not run, as assigned. Commit hooks were skipped because they invoke vp staged; the parent owns integrated verification after the polite relay is restored. Model: openai-codex/gpt-6.1-sol Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Correct the new cross-environment fixture IDs to the existing branded contract and format the two affected test files. Record the origin-first repository identity, selected-repository query and stale-row filtering seams in the fork ledger. The four focused repository/PR files passed 431 tests. After the fixture correction, pullRequestList.logic.test.ts passed 128 tests and the web typecheck passed. Targeted lint passed; the server typecheck retains only the known serverSettings.test.ts:235 preferSchemaOverJson baseline diagnostic. Installed PR-page proof follows the nightly desktop batch. Refs #128 Model: openai-codex/gpt-6-astra Co-authored-by: GPT-6 Astra <noreply@openai.com>
5 tasks
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.
What
Resolve project repository identity from origin before upstream, so a checkout of a fork lists that fork's pull requests. Keep the existing fallbacks when origin is absent.
Read a selected project directly through its explicit repository scope. Reject saved GitHub rows that no longer match the project's current repository, including Authored and Reviewing priority groups. Keep All Projects batching and multi-environment routing.
Why
Refs #128.
The resolver preferred upstream over origin. GitHub requests already use explicit repository selectors and the verified account login, but received the upstream repository identity. Saved rows were checked by project ID, host and state only, so correcting the remote could still leave upstream rows visible until the next answer. A selected unindexed fork also incurred a host search before repeating its repository search.
Testing
Installed nightly source
3ca07c37659338f9fde4142baf50d20f09e4c5d8, version0.0.42-nightly.20261022.39742893669.1. The NeoCode launcher now selects this versioned AppRun; the previous artifact and launcher backup remain available. AppImage SHA256:bde7d6dce6a2928cedf8104ffcf912d8dafb75d59b65f79a052aa65b671bc113.Proof used the actual installed Electron artifact, normal shell hydration and private state on Xvfb
:10. The owner's live window, database and wallet were not used or restarted.PR #130 is delivered. The same private profile/project showed
can1357/oh-my-pibefore the repair andpsychedelicshayna/neopiafter it. The explicit Authored filter now shows the owner's real fork PRs. Explicit project selection with all PR states remains on the fork; upstream rows are absent. GitHub requests in this proof were read-only.The four focused repository/query/filter files passed 431 tests. The corrected cross-environment fixture then passed 128 tests in its affected web file; web types passed. Targeted lint/format passed. Server types retain only the disclosed
serverSettings.test.ts:235baseline diagnostic.Before · After · Authored · Explicit project/all states · Structured proof.
vp checkandvpr typecheckpass (CI runs both; locally run only the checks for the touched scope, perAGENTS.md› Verifying). Focused checks above; no full suite.Model: openai-codex/gpt-6.1-sol. Harness: NeoPi.
Installed integration: GPT-6 Astra in NeoPi; focused execution by GPT-6 Luna.