Repository navigation
fix(history): support Enterprise repositories and omp CLI host alias - #464
Conversation
|
Automated PR review Reviewed head No actionable findings in the reviewed diff Checked all 27 changed files and relevant surrounding callers: repository-selector normalization, selected-server REST/GraphQL routing, capability/principal checks, cache and staging isolation, legacy staging/snapshot compatibility, citations and direct-reference search, selected-source cleanup, the omp-to-Pi CLI alias, adapter guidance, docs/changelog, and the cancellation-retirement regression-test change. Complete source comparisons matched the changed-file diff counts. No existing review discussions were present when checked. Observed CI: all 19 checks returned for this head completed successfully, including Node.js 22/24 test jobs, the path-semantics matrix, and CodeQL. The test jobs report successful build, typecheck, lint, and coverage-test steps (Node.js 22, Node.js 24). Verification limits: static review and observed CI only; candidate code/tests were not executed. Live GitHub Enterprise behavior was not independently exercised; the PR describes deterministic fixture-based Enterprise verification. This comment is not an approval or merge decision. |
Summary
[HOST/]OWNER/REPOhistory sources on GitHub.com and GitHub Enterprise, routing authenticatedghREST/GraphQL requests to the selected host.--host ompas the existingpihost/config/store; keep canonical host configuration unchanged. Update CLI/MCP guidance and documentation.Verification
Qualified commit:
1df0f491ae30c80b9d335468d47080e984cbfbba.pretest:runintact: 2911 passed, 0 failed, 6 skipped.Enterprise behavior was exercised with owned deterministic
ghfixtures, not a live GitHub Enterprise instance. No version bump or release is included.