chore: add product labels in CodeRabbit#12459
Conversation
Mirror the three product labels (product: pnpm, product: pacquet, product: pnpr) from the Qodo config into CodeRabbit, auto-applied based on which stack the diff touches. Enables auto_apply_labels so the labels are attached to the PR rather than only suggested.
Code Review by Qodo
1. Overbroad pnpm label
|
|
Caution Review failedThe pull request is closed. Warning Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesPR Auto-Labeling Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
PR Summary by QodoEnable auto-applied product labels in CodeRabbit config WalkthroughsDescription• Enable CodeRabbit to auto-apply labels directly to PRs. • Add product-scoped labeling rules for pnpm, pacquet, and pnpr diffs. • Mirror existing product-label semantics from the Qodo configuration. Diagramgraph TD
A["PR diff"] --> B["CodeRabbit reviews"] --> C["Labeling rules"] --> D[("GitHub PR labels")]
B --> E["Review guidance"]
High-Level AssessmentThe following are alternative approaches to this PR: 1. Use GitHub Actions labeler (e.g., actions/labeler)
2. Single source of truth + generate bot configs
Recommendation: The PR’s approach is the best fit if CodeRabbit is the desired labeling authority: it keeps the rules close to the CodeRabbit integration and makes labels actually attach via auto_apply_labels. Consider a generator only if label rules expand materially or drift becomes a recurring problem. File ChangesOther (1)
|
| - label: "product: pnpm" | ||
| instructions: "Apply when changes affect the TypeScript pnpm CLI (any code outside pacquet/ and pnpr/)." |
There was a problem hiding this comment.
1. Overbroad pnpm label 🐞 Bug ≡ Correctness
The new "product: pnpm" instruction applies to any change outside pacquet/ and pnpr/, which includes repo-level tooling/config changes (including .coderabbit.yaml itself), so enabling auto_apply_labels will auto-attach an incorrect product label to non-CLI PRs.
Agent Prompt
## Issue description
The `product: pnpm` rule is defined as “any code outside pacquet/ and pnpr/”, which unintentionally includes repo-level files (CI, docs, configs like `.coderabbit.yaml`). With `auto_apply_labels: true`, this will cause noisy/incorrect product labels on non-product PRs.
## Issue Context
This PR enables automatic label application and introduces product labeling rules.
## Fix Focus Areas
- .coderabbit.yaml[7-16]
## Suggested fix
Adjust the `product: pnpm` labeling instruction to target only actual pnpm CLI/source areas (e.g., explicit directories like `pnpm/`, `cli/`, `packages/`, `pkg-manager/`, etc.), or explicitly exclude repo-config-only changes if the schema supports include/exclude path patterns.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Mirror the three product labels from the Qodo config (
.pr_agent.toml) into CodeRabbit (.coderabbit.yaml):product: pnpm— changes to the TypeScript pnpm CLI (anything outsidepacquet/andpnpr/)product: pacquet— changes to pacquet, the Rust port (thepacquet/directory)product: pnpr— changes to pnpr, the registry server (thepnpr/directory andpacquet/crates/pnpr-*crates)CodeRabbit assigns these via
reviews.labeling_instructions, andauto_apply_labels: truemakes it actually attach the labels to the PR rather than only suggesting them in the walkthrough — the equivalent of Qodo'spublish_labels.Written by an agent (Claude Code, claude-opus-4-8).
Summary by CodeRabbit