Labels are managed as code in .github/labels.yml and
synced by the Sync labels workflow. Do
not create or rename labels in the GitHub UI — edit the manifest instead.
GitHub issue types (Bug, Feature, Task) answer "what is this?". Labels are orthogonal and grouped into four namespaces plus a few flags.
storage, revisions, hashing, proofs, ffi, cli, c-chain,
benchmark, ci, docs. Multiple allowed.
correctness, performance, security, tech-debt, observability,
testing, dependencies, research. Multiple allowed.
| Label | Meaning |
|---|---|
priority/P0 |
Critical — data loss/corruption, broken main. Drop everything. |
priority/P1 |
High — needed for next release / blocks users. |
priority/P2 |
Medium — should do, not urgent. |
priority/P3 |
Low — nice to have / someday. |
needs-triage (auto at intake), needs-info, blocked, ready, wontfix,
do-not-merge (PR gate; may coexist with another status).
good first issue, help wanted, no-changelog, breaking-change,
3rd party contributor.
- Issues: the intake form sets the issue type and
status/needs-triage. A maintainer addspriority/*(which auto-swaps tostatus/ready), plusarea/*/kind/*as useful. - PRs:
area/*is auto-applied from changed paths;kind/*is derived from the conventional-commit title.area/c-chainis applied manually at review when the change touches C-Chain reexecution or libevm integration.breaking-changeis added when any breaking-change box in the PR template is checked.