make fmt and make fmt-check do not format Markdown #43

Closed
opened 2026-10-06 14:55:47 +02:00 by clawbot · 0 comments
Collaborator

make fmt and make fmt-check handle Go only. The standard REPO_POLICIES.md (at sneak/prompts dd4027b, which #42 vendors) says Markdown is formatted with prettier, with tabWidth: 4 and proseWrap: always, and that formatting runs on the host through script/fmt and script/fmt-check. This repo's README.md and TODO.md are checked by nothing, so a badly wrapped edit passes the full check.

Found while re-vendoring for #33. Starts after that PR lands, since both change script/fmt.

Definition of done

  • script/fmt also formats every *.md with prettier at the standard settings, and script/fmt-check fails on Markdown prettier would change. Follow the standard script/fmt, script/fmt-check and script/bootstrap at that commit (prettier pinned through package.json and yarn.lock, node pinned in script/bootstrap), keeping this repo's Go formatting steps.
  • .prettierrc (and .prettierignore if the policy asks for it) are copies of the standard files.
  • The existing Markdown is formatted once, in its own commit, with nothing else in it.
  • Negative control, not committed: a badly wrapped line in README.md makes script/fmt-check fail, and script/fmt fixes it.
  • The README Entrypoints entries for script/fmt and script/fmt-check say what they now do. The full check is green.

Implementation requirements

  • No vendored file is loosened, and prettier runs with the standard settings only.
  • Landing commit title must end with (closes #<this issue>).

Model: opus-5-5

`make fmt` and `make fmt-check` handle Go only. The standard `REPO_POLICIES.md` (at `sneak/prompts` `dd4027b`, which https://git.eeqj.de/sneak/simplelog/pulls/42 vendors) says Markdown is formatted with `prettier`, with `tabWidth: 4` and `proseWrap: always`, and that formatting runs on the host through `script/fmt` and `script/fmt-check`. This repo's `README.md` and `TODO.md` are checked by nothing, so a badly wrapped edit passes the full check. Found while re-vendoring for https://git.eeqj.de/sneak/simplelog/issues/33. Starts after that PR lands, since both change `script/fmt`. ## Definition of done - `script/fmt` also formats every `*.md` with `prettier` at the standard settings, and `script/fmt-check` fails on Markdown `prettier` would change. Follow the standard `script/fmt`, `script/fmt-check` and `script/bootstrap` at that commit (`prettier` pinned through `package.json` and `yarn.lock`, node pinned in `script/bootstrap`), keeping this repo's Go formatting steps. - `.prettierrc` (and `.prettierignore` if the policy asks for it) are copies of the standard files. - The existing Markdown is formatted once, in its own commit, with nothing else in it. - Negative control, not committed: a badly wrapped line in `README.md` makes `script/fmt-check` fail, and `script/fmt` fixes it. - The README Entrypoints entries for `script/fmt` and `script/fmt-check` say what they now do. The full check is green. ## Implementation requirements - No vendored file is loosened, and `prettier` runs with the standard settings only. - Landing commit title must end with ` (closes #<this issue>)`. Model: opus-5-5
clawbot self-assigned this 2026-10-06 14:55:47 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/simplelog#43