From bea15ec4472ba4aa954d50f976f4920d7ce4b907 Mon Sep 17 00:00:00 2001 From: Brandon Corbett Date: Thu, 30 Jul 2026 22:42:30 -0400 Subject: [PATCH] fix(format): stop Prettier reformatting the issue templates `prettier --check .` fails on main against `.github/ISSUE_TEMPLATE/`, without anything in the repo having changed. Prettier is ranged at ^3.8.1 and now resolves to 3.9.6, which treats code fences inside markdown differently. What it wants is worse than what is committed: the multi-line placeholder in each template collapses to `z.object({/* ... */});`, which is harder to read than the shape a contributor is meant to copy, and is not how anyone writes it. These templates are prose that GitHub renders. Nothing compiles them, so formatting them buys no consistency worth having, and it leaves the check hostage to how the next Prettier decides to treat embedded code. Verified with npm run format:check, npm run lint, npm run typecheck, and npm test (155 passing). --- .prettierignore | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.prettierignore b/.prettierignore index f7f6b5a..6a48104 100644 --- a/.prettierignore +++ b/.prettierignore @@ -3,3 +3,11 @@ node_modules # Written by changesets; leave its formatting alone so a release cannot fail format:check. CHANGELOG.md + +# Issue templates carry illustrative schema snippets in fenced code blocks, and +# Prettier reformats what is inside those blocks. It collapses a deliberately +# multi-line placeholder into `z.object({/* ... */});`, which is harder to read +# than the shape a contributor is meant to copy. These files are prose rendered +# by GitHub rather than anything compiled, so formatting them gains nothing and +# leaves the check hostage to how a future Prettier treats embedded code. +.github/ISSUE_TEMPLATE/