Worktrees with merge commits no longer fail the history consistency check.
What's wrong with this entry?
The check that verifies a worktree's commit history looks as expected now accepts a commit with any number of parents, provided each one is in the known set, instead of insisting on a fixed three-parent shape. Histories containing merges no longer fail the check.
i.length > jgt
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
worktree.locationsetting for Desktop SSH sessionsBoth mention worktree
-
v2.1.246
Worktree cleanup only removes directories Claude Code created
Both mention worktree
-
v2.1.248
Background sessions adopt an existing worktree at startup
Both mention worktree