Skip to content

chore: add automatic labeling and codeowners - #66

Merged
fwal merged 3 commits into
mainfrom
fwal/labels
Jul 20, 2026
Merged

chore: add automatic labeling and codeowners#66
fwal merged 3 commits into
mainfrom
fwal/labels

Conversation

@fwal

@fwal fwal commented Jul 20, 2026

Copy link
Copy Markdown
Owner
  • Add automatic labeling of PRs based on files touched
  • Add codeowners file to help with reviews

Summary by CodeRabbit

  • Chores
    • Added automated pull request labeling based on branch names, changed areas, documentation, and configuration files.
    • Added workflow automation to apply labels when pull requests are opened or updated.
    • Updated repository code ownership settings to improve review routing.

@fwal fwal self-assigned this Jul 20, 2026
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

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

Next review available in: 52 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: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d3f0417f-322d-4e55-848d-664751318ca1

📥 Commits

Reviewing files that changed from the base of the PR and between 114e71d and 5cf330d.

📒 Files selected for processing (1)
  • .github/workflows/triage.yml
📝 Walkthrough

Walkthrough

Adds GitHub repository governance configuration: a CODEOWNERS assignment, branch and path-based label rules, and a Triage workflow that applies labels when pull requests are opened or synchronized.

Changes

GitHub governance

Layer / File(s) Summary
Pull request labeling automation
.github/labeler.yml, .github/workflows/triage.yml
Defines branch and path-based labels and runs the labeler workflow for eligible pull request events.
Code ownership assignment
.github/CODEOWNERS
Adds a repository code ownership rule.

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

Poem

A rabbit hops through workflows bright,
Labels bloom at pull request night.
Branches whisper, paths align,
Owners guard each changed line.
“Hop!” says the bunny—“CI looks fine!”

🚥 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 summarizes the main changes: automatic labeling and CODEOWNERS additions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/triage.yml:
- Line 19: Update the actions/labeler workflow step to reference a full
immutable commit SHA instead of the mutable `@v6` tag, while preserving the
existing action configuration.
- Around line 3-5: Update the workflow trigger from pull_request to
pull_request_target while preserving the existing opened and synchronize event
types, so actions/labeler@v6 can apply labels to fork-originated pull requests.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b34a6491-73bf-4a7d-8224-120e093506bb

📥 Commits

Reviewing files that changed from the base of the PR and between 7930c3e and 114e71d.

📒 Files selected for processing (3)
  • .github/CODEOWNERS
  • .github/labeler.yml
  • .github/workflows/triage.yml

Comment thread .github/workflows/triage.yml
Comment thread .github/workflows/triage.yml
@fwal
fwal merged commit 988fec1 into main Jul 20, 2026
4 of 5 checks passed
@fwal
fwal deleted the fwal/labels branch July 20, 2026 19:50
@fwal fwal added this to the 1.0 milestone Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant