Skip to content

chore: pin CodeRabbit label vocabulary to the kind/* scheme #687

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rootsongjc merged 1 commit into from
Jul 31, 2026
Merged

chore: pin CodeRabbit label vocabulary to the kind/* scheme #687

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions .coderabbit.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
#
# Label vocabulary for CodeRabbit. Without this file CodeRabbit infers labels
# from past pull requests, which is how the flat `enhancement` label kept coming
# back after it was deleted. With `labeling_instructions` set, CodeRabbit only
# suggests labels from the list below.
#
# Scope is limited to `kind/*` on purpose. `area/*` is applied deterministically
# by path globs in .github/labeler.yml, and `priority/*` is a maintainer call.

reviews:
labeling_instructions:
- label: kind/bug
instructions: Apply when the pull request fixes broken behavior on the site, such as a wrong link, a rendering fault, a build failure, or a script that does not work as documented.
- label: kind/feature
instructions: Apply when the pull request adds new site functionality or a new component, page, or build step. Also apply for performance work that changes how assets are produced or served.
- label: kind/documentation
instructions: Apply when the pull request only changes documentation, blog, tutorial, or translation content, including corrections to prose, tables, and front matter.
- label: kind/cleanup
instructions: Apply when the pull request refactors, reformats, or updates configuration and dependencies without changing behavior for site visitors.
mutually_exclusive_groups:
kind:
- kind/bug
- kind/feature
- kind/documentation
- kind/cleanup
auto_apply_labels: true
Comment on lines +19 to +27

@coderabbitai coderabbitai Bot Jul 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== .coderabbit.yaml =="
cat -n .coderabbit.yaml || true

echo
echo "== occurrences of kind/cleanup and PR objective-ish wording =="
rg -n "kind/(bug|feature|documentation|cleanup)|PR objective|objective|suggest|apply|auto_apply_labels|coderabbit" -S . --glob '!node_modules/**' --glob '!dist/**' --glob '!build/**' || true

Repository: Project-HAMi/website

Length of output: 50376

Resolve the conflicting kind/cleanup label contract.

.coderabbit.yaml now permits and auto-applies kind/cleanup, but the PR objective contracts CodeRabbit to only kind/bug, kind/feature, and kind/documentation. Either remove kind/cleanup from the config or update the objective to explicitly include it.

🤖 Prompt for 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.

In @.coderabbit.yaml around lines 19 - 27, Resolve the label contract mismatch
in the CodeRabbit configuration: either remove kind/cleanup from the mutually
exclusive kind labels and its auto-application rules, or update the related
objective contract to explicitly include kind/cleanup. Keep the configured label
set and objective requirements consistent.

Source: MCP tools