Skip to main content

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/.githublabels/labels.yml

Full documentation: docs/LABELS.md

Available Labels

CategoryExamples
Prioritypriority/critical, priority/high, priority/medium, priority/low
Typeenhancement, bug, documentation, breaking-change, dependencies
Componentcore, api, testing, quality, configuration, integration
Statusneeds-triage, status/in-progress, status/review, status/blocked, status/ready
Specialgood-first-issue, help-wanted, security, performance, area/build

Roll Out Labels to Repositories

All repos at once

  1. Go to winccoa-tools-pack/.githubActions
  2. Run workflow "Fan-out labels to repositories"
  3. Start with dry-run: true to preview — then re-run with dry-run: false
  4. Use strict: true to also delete labels not in labels.yml

Single repo

  1. Run workflow "Run single-target label sync"
  2. Set target-repo to winccoa-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

  1. Edit labels/labels.yml in winccoa-tools-pack/.github
  2. Commit and push to main
  3. 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).