chore(biome): exclude *.code-workspace from formatting

[joeblackwaslike]

Biome was reformatting *.code-workspace files, which VS Code watches — each rewrite triggered a workspace reload loop (the window forgets the open folder on reload). Excluding *.code-workspace from Biome's includes (not via .gitignore) stops the loop. One-line change to biome.json.

Summary by Sourcery

Build:

• Update Biome configuration to ignore *.code-workspace files instead of relying on .gitignore.

[coderabbitai]

Warning

Review limit reached

@joeblackwaslike, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 51 minutes and 17 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 6fd02647-07bb-4f0f-ad54-2239de9ed9f4

📥 Commits

Reviewing files that changed from the base of the PR and between b491ac6 and 8fda3a7.

📒 Files selected for processing (1)

• biome.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/biome-exclude-code-workspace

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch chore/biome-exclude-code-workspace

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Biome configuration to exclude VS Code workspace files (*.code-workspace) from being formatted, preventing reload loops in VS Code.

File-Level Changes

Change	Details	Files
Exclude *.code-workspace files from Biome formatting to avoid VS Code workspace reload loops.	Adjusts the Biome configuration includes/excludes section to ignore files matching the *.code-workspace pattern. Ensures formatting will no longer touch VS Code workspace configuration files so VS Code no longer reloads when Biome runs.	biome.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gemini-code-assist]

Code Review

This pull request updates the Biome configuration in biome.json to exclude .code-workspace files. The reviewer recommended using the standard files.ignore array instead of adding negated patterns to files.includes to ensure a cleaner and more maintainable configuration.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

In Biome, the standard and idiomatic way to exclude files from formatting and linting is to use the files.ignore array rather than adding negated patterns to files.includes. Negating patterns inside includes can be confusing and may lead to unexpected behavior. Using files.ignore makes the configuration much cleaner and easier to maintain.

    "includes": ["**"],
    "ignore": ["**/*.code-workspace", "**/dist", "**/coverage", "**/node_modules"]

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR contains a single-line change to a build configuration file (biome.json) to exclude *.code-workspace files from formatting, which is a routine configuration update with no impact on core logic, security, or functionality.

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team

[anthropicreviewbot]

⚠️ [ai-review] Review couldn't complete — an internal or model-provider error occurred (for example an API key or usage-limit problem). It will retry on your next commit; maintainers can check the function logs.

[codexreviewbot]

⚠️ [ai-review] Review couldn't complete — an internal or model-provider error occurred (for example an API key or usage-limit problem). It will retry on your next commit; maintainers can check the function logs.

[anthropicreviewbot]

⚠️ [ai-review] Review couldn't complete — an internal or model-provider error occurred (for example an API key or usage-limit problem). It will retry on your next commit; maintainers can check the function logs.

[codexreviewbot]

⚠️ [ai-review] Review couldn't complete — an internal or model-provider error occurred (for example an API key or usage-limit problem). It will retry on your next commit; maintainers can check the function logs.