Preview our labels on this page.
This documents our usage of issue labels across bpmn.io and related projects.
In our projects we build upon a set of default labels and define a framework for custom, per-repository labels.
- Labels add important additional meta-data, we don't overuse them
- We are label less per default (no low priority or task labels)
- We use colors to group labels semantically
labels-default.yml
defines labels that are available out of the box, across all our repositories.
# fetch issue view via our task board
curl https://tasks.bpmn.io/wuffle/board/cards > issues.json
# execute the label sync utility:
ACCESS_TOKEN=ghp_PERSONAL_ACCESS_TOKEN_WITH_REPO_SCOPE node index.js
# for debugging purposes run it in `DRY_RUN` mode
DRY_RUN=1 ACCESS_TOKEN=ghp_PERSONAL_ACCESS_TOKEN_WITH_REPO_SCOPE node index.js
labels-additional.yml
showcases some custom labels. Those may be added to individual repositories to reflect domain specific aspects.
We use color for semantic grouping of important aspects, within a repository, but also across repository boundaries.