Uh oh!
There was an error while loading. Please reload this page.
refactor: Move examples/ folder to .github/examples/ - #2020
Conversation
- Replace relative path references to PLANNING.md with descriptive text - Convert placeholder issue reference to documentation note - Prevents lint-and-links CI validation failures on template files These links were template placeholders and not meant to be valid file references.
Add two reusable scripts for managing PR status labels based on review state: - update-pr-changelog-review.js: Full-featured handler that fetches review data and updates labels - update-pr-labels-simple.js: Lightweight label-only updater for quick status sync These scripts automate the process of updating PR status labels (status:needs-review, status:needs-update, etc.) based on actual review progress and PR state, keeping the meta:needs-changelog workflow in sync with real review activity. Supports dry-run, interactive, and auto modes for safe and flexible deployment. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Remove unused hasStatusLabel variable from update-pr-labels-simple.js - Add comprehensive test files for both automation scripts - Update PR template with all required sections (Linked issues, Changelog, Checklist) These scripts automate PR status label updates based on review state and changelog requirements.
- Moved FEEDBACK_RESPONSE_example-*.md files from root examples/ directory - to .github/examples/ directory for better organization - Examples are now nested within the .github folder structure Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Added entry for PR #2015 documenting the two new automation scripts for managing PR status labels based on review progress.
Warning Review limit reached
Next review available in:22 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
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. Comment |
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow. |
🚫 This PR description is missing required template content. Missing required section(s): Linked issues, Global DoD checklist Please update the PR body using one of the repository PR templates:
Empty placeholders, unchecked checklist boxes, and stub issue references do not count. |
🔍 Reviewer Summary for PR #2020CI Status: ✅ Recommendations
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Remove unused beforeEach from update-pr-labels-simple.test.js - Remove unused beforeEach from update-pr-changelog-review.test.js - Both files only use describe, it, expect, and vi Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
ashleyshaw
commented
Aug 18, 2026
Closing in favor of #2023, which contains only the examples folder reorganization without the unrelated commits that were causing CI failures. |
Summary
Reorganizes the examples folder structure for better project organization by nesting it within the .github directory.
Changes
examples/folder from repository root to.github/examples/FEEDBACK_RESPONSE_example-complex.mdFEEDBACK_RESPONSE_example-simple.mdRationale
Nesting the examples folder within the .github directory keeps all github-related content organized together, reducing clutter at the repository root.
Linked issues
N/A - organizational improvement
Changelog
refactor: Move examples/ folder to .github/examples/ for better organizationGlobal DoD checklist
🤖 Generated with Claude Code