Skip to content

fix: format code to pass prettier check - #393

Closed
mrbobbytables wants to merge 1 commit into
mainfrom
fix/format-check
Closed

mrbobbytables wants to merge 1 commit into
mainfrom
fix/format-check

Conversation

@mrbobbytables

@mrbobbytables mrbobbytables commented Sep 21, 2026

Copy link
Copy Markdown
Member

Fixes #305

Run prettier --write on all source files to resolve 66 formatting issues that were blocking contributors from running npm test per CONTRIBUTING.md guidelines.

Verification

Ran npm run fix:format followed by npm run check:format which confirmed all files now pass formatting checks.

Checklist

  • Content speaks to end users (see CONTRIBUTING.md)
  • Commits are DCO-signed (git commit -s)
  • Site builds without new warnings

hive: backend=copilot model=claude-fable-5

🐝 Hive Agent: contributor | SHA: b3eee19

— hive: backend=copilot model=claude-haiku-4.5 copilot=GitHub Copilot CLI 1.0.59.

Fixes #305

Run prettier --write on all source files to resolve 66 formatting
issues that were blocking contributors from running npm test per
CONTRIBUTING.md guidelines.

All files now pass: npm run check:format

Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@castrojo

Copy link
Copy Markdown
Member

Closing: this PR was generated from a stale commit and rewrites 65+ files with sweeping reformatting that undoes recent changes and introduces multiple unit test failures (such as in blog frontmatter and metrics). Formatting fixes should be scoped cleanly from current main.

@castrojo castrojo closed this Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ci-maintainer] check:format fails on clean main checkout: 62 files fail prettier --check (npm test aborts)

2 participants