-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathlabels.yml
More file actions
118 lines (93 loc) · 3.62 KB
/
Copy pathlabels.yml
File metadata and controls
118 lines (93 loc) · 3.62 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
# labelsync's own label catalogue.
#
# This file is both the source of truth for this repository's labels and the
# worked example the documentation refers to. It deliberately satisfies every
# rule in docs/design.md § Validation — most notably that label colours are
# globally unique and descriptions are at most 100 characters.
version: 1
# ── Repository selectors ──────────────────────────────────────────────
groups:
self:
repos:
- specsnl/labelsync
# ── Fallback groups for labels that don't specify any ─────────────────
defaults:
groups: [self]
# ── Migrations from GitHub's stock labels ─────────────────────────────
#
# A rename is a PATCH, so the label keeps its identity and stays on every issue
# and pull request that already carries it. It is emitted only where "from"
# exists and "to" does not — on a repository that already has both, the rename
# has effectively already happened and the stock leftover is left to prune.
renames:
- from: "bug"
to: "type: bug"
- from: "enhancement"
to: "type: feature"
# ── Labels ────────────────────────────────────────────────────────────
labels:
# Area — which part of the codebase an issue touches.
- name: "area: config"
color: "1d76db"
description: "Config loading, validation, group resolution"
- name: "area: palette"
color: "8a63d2"
description: "Colour allocation and candidate generation"
- name: "area: plan"
color: "5319e7"
description: "The pure reconciliation planner"
- name: "area: github"
color: "24292f"
description: "GitHub API client, auth, cache, rate limiting"
- name: "area: cli"
color: "0e8a16"
description: "Cobra commands, flags, output rendering"
- name: "area: ci"
color: "fbca04"
description: "Workflows, rulesets, release pipeline"
- name: "area: docs"
color: "0075ca"
description: "Documentation and README"
# Type — what kind of work it is.
- name: "type: epic"
color: "3f1f78"
description: "Parent tracking issue with sub-issues"
- name: "type: feature"
color: "a2eeef"
description: "New functionality"
- name: "type: test"
color: "bfd4f2"
description: "Test coverage without behaviour change"
- name: "type: chore"
color: "d4c5f9"
description: "Maintenance, tooling, scaffolding"
- name: "type: spike"
color: "e99695"
description: "Time-boxed research; the output is a decision"
- name: "type: bug"
color: "d73a4a"
description: "Something isn't working"
# Readiness — answers "what can I pick up right now?".
- name: "blocked"
color: "b60205"
description: "Waiting on another issue to land"
- name: "parallel-safe"
color: "0052cc"
description: "No unlanded dependencies; safe to start immediately"
- name: "good first issue"
color: "7057ff"
description: "Good for newcomers"
# Referenced by .github/dependabot.yml. Dependabot silently drops labels that
# do not exist, so these have to be declared here to have any effect.
- name: "dependencies"
color: "0366d6"
description: "Dependency updates"
- name: "github-actions"
color: "2088ff"
description: "GitHub Actions dependency updates"
- name: "go"
color: "00add8"
description: "Go dependency updates"
- name: "docker"
color: "2496ed"
description: "Docker dependency updates"