ci: label pull requests from their changed paths - #681
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
✅ Deploy Preview for project-hami ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Issue labels were applied by hand in a single pass, and pull requests carried no area label at all. Path to area mapping does not need judgement, so it can run on its own. Uses pull_request_target because a pull_request run from a fork gets a read-only token and cannot add labels. The workflow never checks out or runs pull request code, it only reads the changed file list. Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
b85b5f2 to
0467b7b
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mesutoezdil, rootsongjc The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
2 participants
Why
Issue labels were applied in a single manual pass. Pull requests carry no
area/*label at all, and nothing keeps either up to date as new work arrives.Mapping a changed path to an area needs no judgement, so it can run on its own. Priority and difficulty still cannot, and are left alone.
What it does
.github/labeler.ymlmaps paths to thearea/*labels.area/docsdocs/,versioned_docs/,versioned_sidebars/,tutorials/,sidebars*.js,versions.jsonarea/uisrc/area/blogblog/area/i18ni18n/area/edge-functionsnetlify/,netlify.tomlarea/ci-infra.github/,scripts/,package*.json, lint and format configarea/seostatic/robots.txt,static/llms.txt,docusaurus.config.jsarea/uiis new, created to coversrc/(React components, pages, theme, css), which is the largest source directory here and had no area label. It uses the same colour as the rest of thearea/*family. Every other label already existed.Dry run against merged pull requests
Ran the rules against the actual changed file lists:
.github/ISSUE_TEMPLATE/*area/ci-infrasrc/pages/index.jsarea/ui.github/workflows/docs-health.ymlarea/ci-infrapackage.json,package-lock.jsonarea/ci-infrai18n/…,tutorials/…,sidebars-tutorials.jsarea/i18n,area/docsEvery merged pull request checked now lands on at least one area.
Notes
pull_request_targetis used because apull_requestrun from a fork gets a read-only token and cannot add labels. The workflow never checks out or executes pull request code, it only reads the changed file list, so the elevated token is not exposed to contributor code. The action is pinned by commit SHA, matching the convention indocs-health.yml.sync-labels: falsemeans labels are only added, never removed, so a manually applied label is not stripped on the next push.npm run format:checkpasses.