docs(gap-baseline): retract false main-history-splice claim (shallow-clone artifact) by seonghobae · Pull Request #1722 · ContextualWisdomLab/.github

seonghobae · 2026-09-02T10:30:37Z

Retraction

This PR originally claimed main's history was spliced onto new roots around 2026-08-20/21, based on 15 PRs (later 16, plus 2 more queued) all hitting fatal: refusing to merge unrelated histories. That claim was wrong.

Root cause: the local .github checkout in the analysis sandbox was a shallow git clone (git rev-parse --is-shallow-repository → true). A shallow clone's truncation-boundary commits present as disjoint history roots (git rev-list --max-parents=0 lists them as fake roots), and git merge from inside a shallow checkout genuinely raises fatal: refusing to merge unrelated histories even when the real, full history is a single connected line — this is real, documented git behavior for shallow clones, which is exactly why it read as convincing evidence of an actual split.

After git fetch --unshallow origin: origin/main has exactly one root commit (0c6e99ed0acab17b1cdd9f853a8398ddb0eed269), and 731af58e (originally claimed "not reachable from current main at all") is a completely normal ancestor.

A Devin Review comment on this PR directly disputed the original claim ("All 15 listed heads share a merge base with current main, and 731af58e is its ancestor") and asked for reproducible evidence — that's what prompted the re-check that found the shallow clone. Thank you for catching this.

Corrective actions taken

Retraction comments posted on all 16 PRs that received the false triage guidance (the original 15, plus fix(scheduler): fall back to REST when auto-rebase GraphQL transport fails #1065 from a second triage pass).
The second triage pass (which was actively applying the same false diagnosis to more PRs) was stopped before it posted beyond fix(pip-audit): keep index-url locks hashed and reject symlink parents #1051 (already covered) and fix(scheduler): fall back to REST when auto-rebase GraphQL transport fails #1065; two more (feat(integration): add ecosystem capability catalogue #1147, fix(strix): bind evidence to exact workflow artifacts #1009) were queued but never posted.
No merges, pushes, or branch rewrites were ever made on the basis of the false diagnosis — the recommended remediation was comment-only by design, which limited the damage to incorrect guidance rather than lost work.
docs/product-technical-gap-baseline.md's entry has been rewritten in place to record the retraction, the real root cause, and a standing lesson: always check git rev-parse --is-shallow-repository (and git fetch --unshallow if true) before diagnosing any multi-root or "unrelated histories" condition on any repo in this ecosystem.

Verification

pytest tests/test_product_technical_gap_baseline.py -q → 5 passed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4

Generated by Claude Code

A triage pass on 15 of the repo's stalest open PRs found every one produces "fatal: refusing to merge unrelated histories" against origin/main -- not an ordinary merge conflict. Independently verified: main now has multiple historical roots, with the splice landing roughly 2026-08-20/21 (PR bases before that window are not ancestors of current main; bases after it are). This changes how future triage on this repo's PR backlog must proceed: check base-SHA ancestry (git merge-base --is-ancestor <base> origin/main) before attempting the standard merge-and-resolve recipe on any PR older than ~2026-08-20/21, since a large fraction of the ~100+ remaining open PRs are likely on the orphaned side and will hit the identical wall. Records the discovery, scope, and recommended per-PR path (re-verify against current main, then re-implement as a fresh branch if still needed) rather than a mechanical fix, since none was safely available. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4

coderabbitai · 2026-09-02T10:30:44Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 6c452eb6-77ac-4def-ad8b-d108dc749059

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…clone artifact) The 2026-09-02 "main's history was spliced ~2026-08-20/21" entry was wrong. The local .github checkout in the analysis sandbox was a shallow clone (git rev-parse --is-shallow-repository -> true); a shallow clone's truncation-boundary commits present as disjoint history roots, and git merge from inside one genuinely raises "fatal: refusing to merge unrelated histories" even when the real, full history is a single connected line. After git fetch --unshallow, origin/main has exactly one root commit and 731af58 (claimed unreachable) is a normal ancestor. A Devin Review comment on this PR directly disputed the original claim and prompted the re-check that found the real cause. Retraction comments were posted on all 16 PRs that received the false triage guidance (15 from the original pass plus one from a second triage pass that was stopped before it could post more); no merges or pushes were ever made on the basis of the false diagnosis. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4

…, not 17) Devin Review caught an internal inconsistency: the entry said "17 open PRs" but listed and later referenced 16. Corrected the count and clarified that the two queued-but-unposted PRs (#1147, #1009) never received a comment and need no retraction reply. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4

…n-history-splice # Conflicts: # docs/product-technical-gap-baseline.md

harbourviewcompany-create · 2026-09-02T23:23:04Z

Evidence log — 2026-09-02

Exact current head: ce4fad9a7e73a8492c4af78df96ec2b9e2c645d0.

Current protected main: 8c085835fbf77de2321b72fa6b8dd946227e523e.
PR base recorded at creation: 8c085835fbf77de2321b72fa6b8dd946227e523e.
Current exact-head Actions are queued: OSV 33659440315, Scorecard 33659439374, SAST 33659439509, Contextual Orchestrator Review Repair Quality CI 33659439433, Secret Scan 33659439389, CodeQL 33659439521, SBOM 33659439465, Security Scan 33659439530, Python Security 33659439338, Noema Reviewer Token Lifetime CI 33659439524.
Combined commit status currently reports CodeRabbit success and Devin Review success; required Actions remain non-terminal.
Focused repository evidence recorded in the PR body is pytest tests/test_product_technical_gap_baseline.py -q → 5 passed.

Gate decision: HOLD. The focused test evidence is positive, but it does not substitute for terminal exact-head required/security/provenance checks. No merge should occur until those checks complete and the live protected-branch/review gates are satisfied.

opencode-agent · 2026-09-04T15:56:46Z

Scheduled review-feedback autofix for this PR head.

Head SHA: 093c39b0070b30bdfc1e62ac8761c98804d213fc

…n-history-splice # Conflicts: # docs/product-technical-gap-baseline.md

seonghobae · 2026-09-05T01:33:07Z

The agent-review-runtime-quality failure reported for 6dcba3d3 (the pre-existing stale hourly-cron/changed-scope test-oracle drift, already fixed on main via #1875/#1877/#1878/#1861) is moot: the branch was auto-updated to current main (b5efbc2762e4) immediately after, landing at ad38c4877 — all checks are now freshly queued against that head. No fix needed here; watching the fresh run.

Generated by Claude Code

…n-history-splice-merge

seonghobae · 2026-09-05T04:49:41Z

agent-review-runtime-quality failed again (17 failures, all in tests/test_pr_review_merge_scheduler.py — TypeError/invalid git sha: 'head' fixture drift) — this branch had drifted "behind" main again since the last update at 01:33 UTC, re-inheriting a stale-fixture issue already fixed upstream. This PR's own diff still only touches docs/product-technical-gap-baseline.md.

Merged current main (bc59c07c4) in again, validated: full suite coverage run -m pytest tests -q → 2841 passed, 1 skipped, 21 subtests passed, zero failures; git diff --check clean. Pushed as e3b0b2d64 (merge commit, no force).

Generated by Claude Code

Both found by an adversarial re-triage of this session's own open PRs, where the classifier made the first error itself -- which is the evidence that the entry is needed. cancelled is not failure. On #933, 22 check runs on head 9988c4f were all completed: 20 cancelled, 2 skipped, ZERO failure, with the combined commit status reading success. An automated triage pass still labelled it CI-red and produced a careful analysis of whose fault a failure was that did not exist. Org-wide the cancelled case dominates -- 18 of the 20 most recent agent-review-runtime-quality-ci.yml runs were cancelled -- so reading the conclusion field rather than the surrounding noise is the whole discipline. The starvation loop is the second half. A bot auto-merging main into a branch on a cadence, against the saturated queue of signature 7, means no check can ever conclude: each new head cancels the runs still queued from the last one. On #1722 opencode-agent[bot] merged main in four times across three days; per-head outcomes were cancelled, failure, failure, cancelled, pending, and run 33945594764 sat queued 4.5 hours without ever executing before the next auto-update killed it. That PR has not completed a check cycle once. Consequences recorded: never tell anyone to wait on a specific queued run id, because on an auto-updated branch it may already be cancelled and a cancelled run cannot produce a conclusion; and do not merge main in yourself in response, since a second updater cannot help a branch already updated faster than the queue absorbs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4

seonghobae marked this pull request as ready for review September 2, 2026 10:48

This comment was marked as resolved.

Sign in to view

seonghobae changed the title ~~docs(gap-baseline): record main's history splice (~2026-08-20/21)~~ docs(gap-baseline): retract false main-history-splice claim (shallow-clone artifact) Sep 2, 2026

This comment was marked as resolved.

Sign in to view

seonghobae mentioned this pull request Sep 2, 2026

feat: add read-only Actions queue health evidence #1150

Open

Merge remote-tracking branch 'origin/main' into docs/gap-baseline-mai…

ce4fad9

…n-history-splice # Conflicts: # docs/product-technical-gap-baseline.md

opencode-agent Bot added 2 commits September 3, 2026 05:49

Merge branch 'main' into docs/gap-baseline-main-history-splice

614bc8b

Merge branch 'main' into docs/gap-baseline-main-history-splice

093c39b

seonghobae and others added 2 commits September 5, 2026 07:21

Merge remote-tracking branch 'origin/main' into docs/gap-baseline-mai…

6dcba3d

…n-history-splice # Conflicts: # docs/product-technical-gap-baseline.md

Merge branch 'main' into docs/gap-baseline-main-history-splice

ad38c48

Merge remote-tracking branch 'origin/main' into docs/gap-baseline-mai…

e3b0b2d

…n-history-splice-merge

Merge branch 'main' into docs/gap-baseline-main-history-splice

88775b6

seonghobae mentioned this pull request Sep 5, 2026

docs(agents): add CI failure-signature triage catalog and index the know-how stores #1913

Open

6 tasks

Merge branch 'main' into docs/gap-baseline-main-history-splice

375013c

Navigation Menu

Uh oh!

docs(gap-baseline): retract false main-history-splice claim (shallow-clone artifact) - #1722

docs(gap-baseline): retract false main-history-splice claim (shallow-clone artifact)#1722
seonghobae wants to merge 11 commits into
mainfrom
docs/gap-baseline-main-history-splice

seonghobae commented Sep 2, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Sep 2, 2026 •

edited

Loading

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

harbourviewcompany-create commented Sep 2, 2026

Uh oh!

opencode-agent Bot commented Sep 4, 2026

Uh oh!

seonghobae commented Sep 5, 2026

Uh oh!

seonghobae commented Sep 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

seonghobae commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Retraction

Corrective actions taken

Verification

Uh oh!

coderabbitai Bot commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

harbourviewcompany-create commented Sep 2, 2026

Evidence log — 2026-09-02

Uh oh!

opencode-agent Bot commented Sep 4, 2026

Uh oh!

seonghobae commented Sep 5, 2026

Uh oh!

seonghobae commented Sep 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

seonghobae commented Sep 2, 2026 •

edited

Loading

coderabbitai Bot commented Sep 2, 2026 •

edited

Loading