Skip to content

chore: checks formatting using local prettier#7

Merged
georgeciubotaru merged 5 commits into
mainfrom
chore/local-prettier
Jul 2, 2026
Merged

chore: checks formatting using local prettier#7
georgeciubotaru merged 5 commits into
mainfrom
chore/local-prettier

Conversation

@teodorus-nathaniel

@teodorus-nathaniel teodorus-nathaniel commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

resolves #6

Summary by CodeRabbit

  • Chores
    • Improved the formatting check step to use the appropriate package manager automatically, helping formatting checks run more reliably across environments.

@teodorus-nathaniel teodorus-nathaniel self-assigned this Jul 2, 2026
@holdex

holdex Bot commented Jul 2, 2026

Copy link
Copy Markdown

Time Submission Status

Member # Time Running Total Status Last Update
teodorus-nathaniel 1 30min 30min Jul 2, 2026, 9:58 AM
teodorus-nathaniel 2 +15min 45min Jul 2, 2026, 10:06 AM
teodorus-nathaniel 45min ✅ Submitted
georgeciubotaru 5min ✅ Submitted Jul 2, 2026, 10:16 AM

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@teodorus-nathaniel, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8f4716cb-3f6c-46e9-af7a-16657b4fb7f2

📥 Commits

Reviewing files that changed from the base of the PR and between dc394e8 and a24e042.

📒 Files selected for processing (2)
  • .github/actions/base/prettier/action.yml
  • ACTIONS.md

Walkthrough

The Prettier composite action's "Check formatting" step now selects the command to run based on the package-manager input, using pnpm exec prettier, npx prettier, or bunx prettier instead of a single hard-coded command.

Changes

Prettier check command update

Layer / File(s) Summary
Conditional prettier check command
.github/actions/base/prettier/action.yml
Replaces the fixed prettier --check --ignore-unknown invocation with a conditional block selecting pnpm exec, npx, or bunx based on package-manager.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

  • holdex/github-actions#3: Also updates the same Prettier composite action to select the runner based on package-manager.

Suggested reviewers: georgeciubotaru

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: using the local Prettier binary for formatting checks.
Linked Issues check ✅ Passed The change makes the CI formatting check use the repository's local Prettier via the package manager, matching issue #6.
Out of Scope Changes check ✅ Passed The PR stays focused on the formatting check command and does not introduce unrelated changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/local-prettier

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@teodorus-nathaniel

Copy link
Copy Markdown
Collaborator Author

@holdex pr submit-time 30m

@teodorus-nathaniel

Copy link
Copy Markdown
Collaborator Author

@holdex pr add-time 15m

@georgeciubotaru

Copy link
Copy Markdown
Contributor

@holdex pr submit-time 5m

@georgeciubotaru georgeciubotaru merged commit e1e0f9e into main Jul 2, 2026
4 checks passed
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.

Problem: prettier format checks are using newest prettier version

2 participants