chore: add prettier config and CI auto-formatter#166
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
yyovil has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
| @@ -1 +1,3 @@ | |||
| use flake | |||
| entire enable --agent claude-code | |||
There was a problem hiding this comment.
Split this into a separate envrc file that stays only on my system and drop these suggested code changes. Rest of the team doesn't use entire cli for agent session audits.
| @@ -0,0 +1,9 @@ | |||
| { | |||
| "useTabs": false, | |||
There was a problem hiding this comment.
plz useTabs. turn this to true.
There was a problem hiding this comment.
this doesn't belong here. It belongs to my fork only. out of PR's scope. remove this.
There was a problem hiding this comment.
yyovil has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
yyovil has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
Adds .prettierrc and .prettierignore (config only, no local enforcement). Formatting runs in CI via the prettier.yml workflow: on every push to a non-main branch, Prettier rewrites changed files and commits the result back using GITHUB_TOKEN. Developers never need to run Prettier locally. Intentionally excludes husky/lint-staged — local pre-commit hooks are the wrong layer for a formatter that the whole team doesn't need installed. Also adds .envrc.local to .gitignore for personal local shell overrides. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Entire-Checkpoint: 27336650d2ee
yyovil
force-pushed
the
chore/prettier-ci
branch
from
a3dd606 to
5839fae
Compare
There was a problem hiding this comment.
yyovil has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
yyovil has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Resolves conflicts with main's prettier config + CI auto-formatter (#166): - Adopt main's .prettierrc (tabs) — CI reformats every push, so the branch's spaces config would just get rewritten - Take main's versions of frontend/src/landing/** (branch only had formatting changes there; now byte-identical to main) - Keep the branch's frontend/package.json, tsconfig.json, main.ts (the Electron redesign), root package.json (husky/lint-staged), and .gstack/ gitignore entry; keep main's .envrc.local entry - Reformat the branch's own files with prettier@3 exactly as CI does, so the auto-formatter has nothing to commit after push Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 participant
What
Adds Prettier config with CI-driven auto-formatting. Splits the formatter setup out of #156 which bundled it with the React renderer (see review comment there).
How it works
.prettierrc— the only hand-written config (120-char print width, double quotes, trailing commas).prettierignore— excludes generated files (schema.ts,openapi.yaml), lockfiles, andbackend/(Go usesgofmt).github/workflows/prettier.yml— on every push to a non-main branch, runsprettier --write .and commits any changed files back viaGITHUB_TOKENNo local enforcement. No husky, no lint-staged. Developers never need to run Prettier. The formatted output shows up as a CI commit on the branch, not as local uncommitted changes.
GitHub Actions does not re-trigger workflows on commits made with
GITHUB_TOKEN, so there is no feedback loop.After merge
The first push to any feature branch will trigger a formatting pass over the whole codebase. That single CI commit is the mass-reformat — it comes from the bot, not from any developer's machine.
🤖 Generated with Claude Code