Label Workflow ā dakota-iso#
dakota-iso uses Prow (cncf/prow-github-actions v3.5.0) and org-wide configuration from projectbluefin/.project/prow.yaml.
Full org lifecycle documentation lives in the shared Project Bluefin label-workflow guide.
The merge backstop runs sweep lgtm every four hours at minute 11, trading
scheduled runner use for up to four hours of reconciliation delay plus GitHub
scheduling delays. Label sync runs separately on Sundays at 03:11 UTC; manual
dispatch and repository-config pushes still sync labels.
Issue lifecycle#
- Filed. New issues receive
needs-humanand their initialkind/label from the issue template. - Triage. Maintainers review the issue, refine the
kind/*label, and set/areaor/priority. - Accepted. When scope is clear and approved, comment
/triage accepted. - Agent pickup. Maintainers remove
needs-humanwhen work is open for automation. Hive assigns work only whentriage/acceptedis present and neitherneeds-humannorblockedis set. - Blocked. Use
/label blockedwhile waiting on dependencies outside the repo;/remove-label blockedwhen unblocked.
PR lifecycle#
- Opened. Reviewers are requested from
OWNERS. - Review. Reviewers comment
/lgtmwhen satisfied. Any new push clearslgtm. - Approve. An
OWNERSapprover comments/approve(or approves via GitHub review). - Merge. When checks pass with
lgtmandapproved, Prow merges the PR via squash merge. - Hold. Comment
/holdto pause merge;/hold cancelto resume.
Active label taxonomy#
| Category | Labels | Applied by |
|---|---|---|
| Kind | kind/bug, kind/feature, kind/cleanup, kind/documentation, kind/regression, kind/security | Template or /kind <name> |
| Area | area/desktop, area/flatpak, area/gaming, area/hardware, area/installer, area/dx | /area <name>, /remove-area <name> |
| Triage | triage/accepted, needs-triage, needs-kind | /triage accepted, Prow required-label checks |
| Priority | priority/critical-urgent, priority/important-soon | /priority <level> |
| Gates | needs-human, hold, blocked, lgtm, approved | Maintainers, /hold, /label blocked, /lgtm, /approve |
PR comment policy#
(Inherited from org-level model in common/docs/factory/agentic-model.md)
- One comment per PR event, max. Combine all findings into one comment.
- Never duplicate GitHub UI state (approvals, CI status, labels).
@mentions only when asking someone to do something specific.- When in doubt, post nothing. Never post multiple comments on the same issue/PR.