Repository navigation
fix: follow cd/Set-Location for merge and commit checks, release 1.8.5 - #93
Merged
Merged
Conversation
A coordinator in its own worktree (fullops/coor in KnowsLink) merges in the original checkout with `cd <path> && git merge` or `Set-Location <path>; git merge`. The merge SHA advice only followed `git -C`, saw the coordinator's branch and skipped the check. A shared harness_gate.git_calls now tracks cd, chdir, pushd, Set-Location, sl and Push-Location within the command for both the merge advice and the unlinked evidence commit check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
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.
KnowsLink coordinator runs in the
fullops/coorworktree and merges in the original checkout (merge origin/fullops/devon main). 1.8.4's merge SHA advice only followedgit -C, socd <path> && git mergeorSet-Location <path>; git mergewas judged on the coordinator branch and skipped.harness_gate.git_calls: per git command, the checkout it runs in, trackingcd/chdir/pushd/Set-Location/sl/Push-Locationin the same command plusgit -C. Used byintegration.merge_driftand the unlinked evidence commit check.cdandSet-Locationgets the advice; a merge on its own branch does not.npm testpassed.🤖 Generated with Claude Code