ci(pr-automation): stale prs and issues, pr heading and body checker, labels

[Ryan-Millard]

Updated stale issue and PR messages, added days before stale and close settings, and exempt labels.

What was changed & why

• A new simple workflow to manage stale issues & PRs.
  • This helps maintainers by allowing a workflow to warn and close these instead of the current manual setup.
• Automatic PR labeler
• PR validator
  • Ensures correct content remains in the PR

Changes

• stale.yml
• pr-auto-label.yml
• pr-check.yml

Testing & Verification

I ran it on a private repository. It worked as expected.

Additional Resources

None.

Summary by CodeRabbit

• Chores

  • Automated maintenance: marks inactive issues/PRs stale after 60 days and closes them 14 days later; runs daily and supports manual triggering while preserving pinned/important items and applying distinct labels.
  • Auto-labeling: adds automatic PR labeling based on changed file patterns (languages, docs, CI, JS/TS, etc.).
  • PR validation: enforces PR title/body format and requires an explicit issue reference or "none".

• Documentation

  • PR template clarified to prompt an issue reference or "none".

[coderabbitai]

Warning

Rate limit exceeded

@Ryan-Millard has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 35 minutes and 42 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

Adds GitHub automation: a scheduled stale workflow, PR validation workflow, PR auto-label workflow, labeler configuration, and a small PR template tweak requiring an issue placeholder or none. Workflows run daily or on PR events and use GitHub Actions for labeling, stale handling, and validation.

Changes

Cohort / File(s)	Summary
Workflows — stale .github/workflows/stale.yml	New scheduled + manual workflow using actions/stale@v10 to mark issues/PRs stale after 60 days and close after 14 days; applies no-issue-activity / no-pr-activity, exempts pinned and important, grants write perms for issues & pull-requests.
Workflows — PR validation .github/workflows/pr-check.yml	New "PR Validation" workflow with title-check and body-check jobs enforcing conventional-style PR titles, required PR body sections, and requiring an issue reference or explicit none; uses actions/github-script@v7.
Workflows — auto-label .github/workflows/pr-auto-label.yml	New PR-triggered workflow (runs on pull_request_target) using actions/labeler@v6 to assign labels based on changed paths; sets required permissions and uses secrets.GITHUB_TOKEN.
Labeler config .github/labeler.yml	New labeler mappings for C/C++, docs, CI, JS/TS (includes Vite patterns and common package manifest/lockfile matches).
Template .github/PULL_REQUEST_TEMPLATE.md	Minor edit: changed Fixes: line to include #<issue-number> placeholder and guidance to use Fixes: none when no related issue exists.

Sequence Diagram(s)

sequenceDiagram
  participant Contributor
  participant GitHub as "GitHub Events"
  participant Labeler as "actions/labeler@v6"
  participant PRCheck as "PR Validation (github-script)"
  participant Stale as "actions/stale@v10"

  Contributor->>GitHub: open or update PR
  GitHub->>Labeler: trigger pr-auto-label job (reads `.github/labeler.yml`)
  Labeler-->>GitHub: apply labels to PR
  GitHub->>PRCheck: run title-check and body-check jobs
  PRCheck-->>GitHub: report pass/fail statuses

  Note over GitHub,Stale: scheduled maintenance (daily)
  Stale->>GitHub: mark stale / close issues & PRs per config

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• chore(PR templates): fix PR templates - old ones were too busy #235 — also modifies .github/PULL_REQUEST_TEMPLATE.md, closely related to the template change here.

Poem

🐇 I hop through repos in moonlit code,

I label, nudge, and close the quiet road,
I check each title, tidy each plea,
I mark the stale and set the issues free,
A carrot-coded cheer for automation's glow.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main changes: adding CI automation for stale PRs/issues, PR validation checks, and automatic labeling.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/stale-issues-prs

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In @.github/workflows/stale.yml:
- Around line 1-4: Run Prettier on the workflow file to fix CI style errors:
format the YAML using your project's Prettier config (e.g., run prettier --write
on the workflow file or use the repo's formatting npm script) and commit the
resulting changes so the CI lint check for the stale workflow passes; the fix
targets the top-level workflow YAML content (the stale workflow header/comments)
that currently fails formatting.
- Line 20: The workflow currently pins the stale action to "uses:
actions/stale@v5" which targets Node 16 and is no longer supported; update that
reference to a supported release (recommend "actions/stale@v9" for Node 20 or
"actions/stale@v10" for Node 24) and then review and adjust any action inputs in
the workflow to match the new input schema/field names from the actions/stale
release notes; locate the literal string "uses: actions/stale@v5" in the
workflow and replace the version, then run a dry workflow or linter to ensure
the updated inputs (if any) for the stale action (e.g., labels, exempt teams,
days-before-stale, etc.) conform to the v9/v10 schema.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/stale.yml:
- Line 29: The workflow uses the deprecated input exempt-labels for
actions/stale@v10; replace it with the new inputs exempt-issue-labels and
exempt-pr-labels and set them to the same CSV values currently used (e.g.,
"pinned,important"). Update the job step referencing exempt-labels to instead
pass exempt-issue-labels: "pinned,important" and exempt-pr-labels:
"pinned,important" so the action accepts exemptions for both issues and PRs.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/pr-auto-label.yml:
- Around line 8-21: The workflow's Labeler step uses actions/labeler@v4 which is
unsupported; update the step in the label job to actions/labeler@v6 (e.g.,
actions/labeler@v6 or v6.0.1) and keep the existing inputs (repo-token) but
after updating, validate and, if needed, adapt your .github/labeler.yml config
to the v5+ schema changes; locate the "label" job and the step that references
actions/labeler@v4 to make this change.

[Ryan-Millard]

@CodeRabbit full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[Ryan-Millard]

@CodeRabbit where is the review?

[coderabbitai]

@Ryan-Millard: I apologize for the confusion. Let me trigger a comprehensive review of all the changes in this PR right now. You should see detailed inline comments on each of the modified files shortly.

✅ Actions performed

Full review triggered.