chore: keep prettier out of the per-session worktrees - #155
Merged
Merged
Conversation
A worktree under .claude/worktrees/ holds a second copy of the whole tree, so prettier reads every path again under a prefix no rule below matches: `src/content/` does not cover `.claude/worktrees/<name>/src/content/`. CMS content that is deliberately exempt on main therefore reddened `format:check` from inside a worktree. Absent in CI, so this only ever affected someone running the worktree workflow locally. Scoped to the worktrees path rather than `.claude/`, so the tracked skill-context.md stays covered -- checked by breaking its formatting and confirming format:check still fails on it.
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
1 participant
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.
npm run format:checkfails from inside a git worktree, on files that are deliberately exempt onmain.A worktree under
.claude/worktrees/holds a second copy of the whole tree, so prettier walks every path a second time under a prefix that no existing rule matches..prettierignoreexemptssrc/content/because the issue-form intake and Sveltia CMS emit their own frontmatter style — but that pattern does not cover.claude/worktrees/<name>/src/content/, so the same CMS content comes back as a violation:CI never sees this: there is no
.claude/worktrees/on a runner, which is whyformat:checkis green on every PR. It only costs whoever is running the worktree workflow locally, where it reads as a real failure on a file they did not touch.Scoped to
.claude/worktrees/rather than.claude/, because.claude/skill-context.mdis tracked and should stay formatted.Verification
npm run format:checkexits 0 in a checkout that has a worktree present; before, exit 1..claude/skill-context.mdstill failsformat:check, so the tracked file remains covered.