Skip to content

fix: use schema-valid 'default' object in .contributors.yml - #47

Merged
smorin merged 2 commits into
mainfrom
fix/contributors-schema
Jul 16, 2026
Merged

fix: use schema-valid 'default' object in .contributors.yml#47
smorin merged 2 commits into
mainfrom
fix/contributors-schema

Conversation

@smorin

@smorin smorin commented Jul 16, 2026

Copy link
Copy Markdown
Owner

First Update Contributors run failed: Unknown config key(s): /classification/default_category. The schema requires classification.default as an {id, label} object (cross-checked against smorinlabs/py-launch-blueprint's working config). https://claude.ai/code/session_014DjTALJi3LJhYmrdpw6Rej

Review in cubic

The contributors-please schema requires classification.default as an
{id, label} object; default_category is an unknown key and failed the
first Update Contributors run.

Claude-Session: https://claude.ai/code/session_014DjTALJi3LJhYmrdpw6Rej
Copilot AI review requested due to automatic review settings July 16, 2026 07:00
@cursor

cursor Bot commented Jul 16, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 24 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: 018f0666-b174-4029-8bd4-4876c6b73ded

📥 Commits

Reviewing files that changed from the base of the PR and between 55395a4 and 18c98c0.

📒 Files selected for processing (2)
  • .contributors.yml
  • PROJECTS.md

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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the contributors-please configuration to match the tool’s schema requirements for the default classification category, fixing the “Unknown config key(s): /classification/default_category” failure during the Update Contributors workflow.

Changes:

  • Replaced classification.default_category: code with a schema-valid classification.default object containing { id, label }.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@smorin
smorin merged commit d8c08ed into main Jul 16, 2026
21 of 22 checks passed
@smorin
smorin deleted the fix/contributors-schema branch July 17, 2026 05:16
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.

2 participants