From ee61698c3881e11bf867af0b3b3b2cde3ad835f6 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 20 Oct 2026 15:58:23 +0000 Subject: [PATCH 1/4] docs(workspace): compare the merge base with the full SHA (N2) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The compare API returns the full 40-character merge-base SHA, so an abbreviated never equals it and reads as a false "not in main". Say to compare with git rev-parse . Finding N2 of C8's review 452/6279333662, offered unowned in #419 6294331040 item 3. Dylan Roy — delegated AI work; performer Anthropic Claude, session session_01NMeKEismAyeqgdB4sy2NJU. Scientific effect NONE. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NMeKEismAyeqgdB4sy2NJU --- docs/WORKSPACE.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/WORKSPACE.md b/docs/WORKSPACE.md index 7c61373bf..522e11e5c 100644 --- a/docs/WORKSPACE.md +++ b/docs/WORKSPACE.md @@ -138,9 +138,11 @@ Where `--unshallow` is refused, deepen in steps with `git rev-parse --is-shallow-repository` prints `false`, a "yes" from `--is-ancestor` is reliable but a "no" is not. -The commit is in `main` exactly when that merge base equals `` (status -`ahead` or `identical`). A 404 alone proves nothing: GitHub also answers 404 for -a mistyped SHA, a missing branch or a repository the caller cannot see. Treat an +The commit is in `main` exactly when that merge base equals the full +40-character SHA of the commit (status `ahead` or `identical`). The API always +returns the full SHA, so compare it with `git rev-parse `: an abbreviated +`` never matches and would read as a false "not in `main`". A 404 alone +proves nothing: GitHub also answers 404 for a mistyped SHA, a missing branch or a repository the caller cannot see. Treat an unexplained 404 as inconclusive. To establish unrelated history, use a complete clone in which both commits resolve (`git cat-file -e ^{commit}`) and `git merge-base origin/main` prints nothing. From 75698a16b77271ac5c1f98e2ac3ac3317d47ce36 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 20 Oct 2026 15:58:36 +0000 Subject: [PATCH 2/4] docs(workspace): rewrap the N2 paragraph Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NMeKEismAyeqgdB4sy2NJU --- docs/WORKSPACE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/WORKSPACE.md b/docs/WORKSPACE.md index 522e11e5c..72c6ffac8 100644 --- a/docs/WORKSPACE.md +++ b/docs/WORKSPACE.md @@ -142,8 +142,8 @@ The commit is in `main` exactly when that merge base equals the full 40-character SHA of the commit (status `ahead` or `identical`). The API always returns the full SHA, so compare it with `git rev-parse `: an abbreviated `` never matches and would read as a false "not in `main`". A 404 alone -proves nothing: GitHub also answers 404 for a mistyped SHA, a missing branch or a repository the caller cannot see. Treat an -unexplained 404 as inconclusive. To establish unrelated history, use a complete +proves nothing: GitHub also answers 404 for a mistyped SHA, a missing branch or +a repository the caller cannot see. Treat an unexplained 404 as inconclusive. To establish unrelated history, use a complete clone in which both commits resolve (`git cat-file -e ^{commit}`) and `git merge-base origin/main` prints nothing. From 739d9f3ab329f37bdedd28383b5f2b26c2249e52 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 20 Oct 2026 15:58:47 +0000 Subject: [PATCH 3/4] docs(workspace): finish rewrapping the N2 paragraph Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NMeKEismAyeqgdB4sy2NJU --- docs/WORKSPACE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/WORKSPACE.md b/docs/WORKSPACE.md index 72c6ffac8..abaab895e 100644 --- a/docs/WORKSPACE.md +++ b/docs/WORKSPACE.md @@ -143,8 +143,8 @@ The commit is in `main` exactly when that merge base equals the full returns the full SHA, so compare it with `git rev-parse `: an abbreviated `` never matches and would read as a false "not in `main`". A 404 alone proves nothing: GitHub also answers 404 for a mistyped SHA, a missing branch or -a repository the caller cannot see. Treat an unexplained 404 as inconclusive. To establish unrelated history, use a complete -clone in which both commits resolve (`git cat-file -e ^{commit}`) and +a repository the caller cannot see. Treat an unexplained 404 as inconclusive. To +establish unrelated history, use a complete clone in which both commits resolve (`git cat-file -e ^{commit}`) and `git merge-base origin/main` prints nothing. Ancestry shows only that a commit landed. Work carried onto `main` in a new From 8ba9bf2afb71c3b91b4f2de2874063f070b30a1d Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 20 Oct 2026 15:59:00 +0000 Subject: [PATCH 4/4] docs(workspace): finish rewrapping the N2 paragraph (last line) Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NMeKEismAyeqgdB4sy2NJU --- docs/WORKSPACE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/WORKSPACE.md b/docs/WORKSPACE.md index abaab895e..1f7fe80be 100644 --- a/docs/WORKSPACE.md +++ b/docs/WORKSPACE.md @@ -144,8 +144,8 @@ returns the full SHA, so compare it with `git rev-parse `: an abbreviated `` never matches and would read as a false "not in `main`". A 404 alone proves nothing: GitHub also answers 404 for a mistyped SHA, a missing branch or a repository the caller cannot see. Treat an unexplained 404 as inconclusive. To -establish unrelated history, use a complete clone in which both commits resolve (`git cat-file -e ^{commit}`) and -`git merge-base origin/main` prints nothing. +establish unrelated history, use a complete clone in which both commits resolve +(`git cat-file -e ^{commit}`) and `git merge-base origin/main` prints nothing. Ancestry shows only that a commit landed. Work carried onto `main` in a new commit, such as a refresh, has a new SHA, so compare its blobs instead: