Repository navigation
chore: set up auto-labeling for new issues and PRs #696
Description
Part of #690
Set up GitHub Actions workflows that automatically label new issues and PRs, so nothing falls through the cracks and triage stays visible.
Issues: auto-apply status/needs-triage
Every new issue gets status/needs-triage on open. Triager then adds kind/*, area/*, priority/* and removes status/needs-triage.
PRs: auto-apply area/* based on changed files
Use a labeler config (e.g. actions/labeler) to detect which parts of the codebase a PR touches and apply the corresponding area/* labels automatically.
Proposed mapping:
| Path pattern | Label |
|---|---|
burr/core/** |
area/core |
burr/tracking/** |
area/tracking |
burr/integrations/** |
area/integrations |
burr/visibility/** |
area/visualization |
telemetry/ui/** |
area/ui |
website/** |
area/website |
.github/**, scripts/** |
area/ci |
examples/** |
area/examples |
burr/core/typing.py, burr/integrations/pydantic.py |
area/typing |
burr/core/persistence.py, burr/tracking/server/s3/** |
area/storage |
PRs: auto-apply pr/needs-rebase on merge conflicts
When a PR becomes unmergeable, auto-apply pr/needs-rebase. Remove it when the conflict is resolved.
Acceptance criteria
- New issues get
status/needs-triageon open - PRs get
area/*labels based on changed files - PRs get
pr/needs-rebasewhen they have merge conflicts
Activity
andreahlert commentedon Mar 28, 2026
Labels migrated to new taxonomy (#692).
[-]chore: set up auto-labeling for new issues[/-][+]chore: set up auto-labeling for new issues and PRs[/+]ci: add auto-labeling for new issues and PRs
ci: repo governance workflows and assignment policy (apache#713)