3 labels
Sort
Sort
-
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement. -
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management. -
overdue
-
Organization-level labels that can be used with all repositories under this organization
-
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain. -
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history. -
auto/claimed-implementer
Currently being processed by an implementer worker. -
auto/claimed-merge
Currently being processed by the merge driver. -
auto/claimed-reviewer
Currently being processed by a reviewer worker. -
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick. -
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness. -
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml. -
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml. -
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED. -
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally. -
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report. -
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver. -
auto/needs-implementer
Failing CI needs implementer attention. -
auto/postmortem
Documenting a driver incident or rollback. -
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES. -
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history. -
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver. -
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it. -
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch. -
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage. -
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first. -
Bounty$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue -
Bounty$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue -
Bounty$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue -
Bounty$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue -
Bounty$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue -
Bounty$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue -
Bounty$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue -
Bounty$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue -
Bounty$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue -
Bounty$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue -
MoSCoWCould have
Could have feature in order to satisfy the epic/legendary. -
MoSCoWMust have
Must have feature in order to satisfy the epic/legendary. -
MoSCoWShould have
Should have feature in order to satisfy the epic/legendary. -
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity. -
Points1
1 man-hours worth of work for an expert with no learning curve. -
Points13
13 man-hours worth of work for an expert with no learning curve. -
Points2
2 man-hours worth of work for an expert with no learning curve. -
Points21
21 man-hours worth of work for an expert with no learning curve. -
Points3
3 man-hours worth of work for an expert with no learning curve. -
Points34
34 man-hours worth of work for an expert with no learning curve. -
Points5
5 man-hours worth of work for an expert with no learning curve. -
Points55
55 man-hours worth of work for an expert with no learning curve. -
Points8
8 man-hours worth of work for an expert with no learning curve. -
Points88
88 man-hours worth of work for an expert with no learning curve. -
PriorityBacklog
This ticket has backlogged priority and is not to be worked on yet -
PriorityCI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges -
PriorityCritical
The priority is critical -
PriorityHigh
The priority is high -
PriorityLow
The priority is low -
PriorityMedium
The priority is medium -
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed. -
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed. -
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed. -
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design. -
StateCompleted
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed. -
StateDuplicate
A ticket that represents the same content as an existing ticket. -
StateIn Progress
A ticket that is actively being developed. -
StateIn Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in. -
StatePaused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay. -
StateUnverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo. -
StateVerified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog. -
StateWont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt. -
TypeAutomation
Any edits or discussion about the AI automated coding system. -
TypeBug
Something that doesnt work as intended. -
TypeDiscussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories. -
TypeDocumentation
An error or improvement needed in the documentation. -
TypeEpic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics. -
TypeFeature
Some new functionality not present. -
TypeLegendary
A type of Epic which will contain other Epics. -
TypeRefactor
A code change that restructures existing code without changing its external behavior. -
TypeSupport
Someone needs help using the project. -
TypeTask
A generic task that doesnt fit into the other type categories. -
TypeTesting
Work exclusively focusing on fixing or expanding testing.