Labels
All labels across the organization are defined in a single source of truth.
Never create ad-hoc labels directly in a repository — use the rollout workflow instead.
Source of Truth
winccoa-tools-pack/.github → labels/labels.yml
Full documentation: docs/LABELS.md
Available Labels
| Category | Examples |
|---|---|
| Priority | priority/critical, priority/high, priority/medium, priority/low |
| Type | enhancement, bug, documentation, breaking-change, dependencies |
| Component | core, api, testing, quality, configuration, integration |
| Status | needs-triage, status/in-progress, status/review, status/blocked, status/ready |
| Special | good-first-issue, help-wanted, security, performance, area/build |
Roll Out Labels to Repositories
All repos at once
- Go to
winccoa-tools-pack/.github→ Actions - Run workflow "Fan-out labels to repositories"
- Start with
dry-run: trueto preview — then re-run withdry-run: false - Use
strict: trueto also delete labels not inlabels.yml
Single repo
- Run workflow "Run single-target label sync"
- Set
target-repotowinccoa-tools-pack/<repo-name>
Add a new repo to the rollout
Edit repos.txt in the .github repo — one org/repo per line.
Add or Change a Label
- Edit
labels/labels.ymlinwinccoa-tools-pack/.github - Commit and push to
main - Run the fan-out workflow to apply across all repos
Quick Fix via CLI (one-off)
# Create a missing label in one repo
gh label create "priority/high" --color "eb6420" --description "Important for milestone success" --repo winccoa-tools-pack/<repo>
# Edit an existing label
gh label edit "needs-triage" --color "FBCA04" --repo winccoa-tools-pack/<repo>
Quick fixes do not update
labels.yml. Always follow up with a proper edit to keep the source of truth in sync.
Required Secret
The rollout workflows require the org secret ORG_LABELS_PAT (scope: repo).