Files
orca/src/shared/git
Jinjing c9c1960ffb fix(github): discover configured push heads without unsafe merge claims (#41205)
* fix(github): attach PRs from configured push heads and rebased-away heads

Branch PR discovery only tried origin's same-named branch and %(upstream).
A fork reached through a separate pushurl, branch.<name>.pushRemote,
remote.pushDefault, or a push refspec publishing under another name never
matched, so the workspace never attached its PR.

- After those lookups miss, read where a plain push publishes the branch
  (the review branch source GitLab already uses) and look up that head's
  repository + branch. Push URLs resolve through SSH aliases and
  authenticated Enterprise hosts.
- A merged PR whose head was rebased and force-pushed from another
  checkout no longer lists the old commit in commits/{sha}/pulls; check
  the PR's force-push history so a checkout still at that commit keeps
  the merged PR.

* test(github): register push-head mocks at current feature owners

* style(github): consolidate repository probe imports

* fix(github): preserve exact push identity and uncertain review history

* test(github): verify upstream publication through a separate push URL

* fix(github): use fetch identity when resolving review default branches

* fix(github): separate historical association from merged containment proof

* fix(github): separate publish eligibility from existing review discovery

* fix(git): keep explicit refspec precedence in push destination proof

* fix(github): honor upstream admission and filtered force-push pagination

* fix(github): keep local and incomplete upstreams out of hosted push inference
2026-11-14 13:09:38 -08:00
..