docs: git cherry cannot detect a squash-merged branch - #65
Merged
Conversation
CLAUDE.md told you to use `git cherry -v main <branch>` to tell a squash-merged branch from one carrying real work. It cannot: the squashed commit's patch-id matches no individual commit, so every commit shows `+` and a fully-absorbed branch reads as unmerged. Confirmed on D58's 13-commit branch, whose content was byte-identical to main. `git diff main <branch>` answers it directly — empty means absorbed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
handamade
enabled auto-merge (squash)
July 31, 2026 23:51
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.
CLAUDE.mdtold you to usegit cherry -v main <branch>to tell a squash-merged branch from one carrying real work. It cannot.Under squash-merge the single squashed commit carries the combined diff, so its patch-id matches no individual commit on the branch. Every commit shows
+— reading as "still carries work" when the branch is fully absorbed. Confirmed while cleaning up D58: all 13 commits showed+, whilegit diff main d58-menu-dismissalwas empty.git diff main <branch>answers the actual question directly: empty output means the content is fully inmainand the branch is safe to delete.Docs only — no code change, no changeset.
🤖 Generated with Claude Code