ci: add prettier format check - #62
Merged
Merged
Conversation
Add a Format check CI job and a format:check script (prettier --check .) so formatting drift is caught on every PR. The repo already conforms to the local .prettierrc.json added in #59. Add .prettierignore for build output, node_modules, and the generated package-lock.json.
jstirnaman
temporarily deployed
to
cloud-serverless
June 8, 2026 16:25 — with
GitHub Actions
Inactive
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.
What this does
Adds a CI gate so prettier formatting drift is caught on every PR. #59 added the repo-local
.prettierrc.jsonand normalized the tree; this PR enforces it going forward.format-checkjob inci.ymlrunsnpm run format:check(prettier --check .). It reuses the same SHA-pinnedactions/checkoutandactions/setup-nodeas the other jobs.format:checknpm script..prettierignoreforbuild/,node_modules/, and the generatedpackage-lock.json.Why
The repo had no local prettier config, so
prettier --write .inherited an ancestor config and could reformat the whole tree. #59 pinned a local config; without a CI check, nothing prevents future drift.Verification
npm run format:checkpasses locally:All matched files use Prettier code style!