Labels and Triage: How We Organize Issues and PRs #124
julianknutsen
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We've introduced a label system to help everyone — contributors and maintainers — understand where things stand. This post explains what each label means and what to expect when you file an issue or submit a PR.
Every triaged item gets at least a status, a priority, and a kind label.
Status Labels — Where Is This in the Pipeline?
Status labels track where an issue or PR sits in the triage process.
status/needs-triageInbox. Not yet reviewed by a maintainer. Applied automatically to new issues and PRs.
Nothing to do — sit tight. We aim to respond within a week, but this is a volunteer project and it may take longer.
status/needs-infoWaiting on you. We need more information before we can act on this.
Read the maintainer's comment and reply with what was asked. Issues may be auto-closed after a period of silence.
status/needs-reproCan't reproduce. We believe there's a bug but can't trigger it ourselves.
Provide a minimal reproduction — fresh rig, exact steps,
gc doctoroutput, relevant logs. May be auto-closed after a period of silence.status/acceptedConfirmed. Maintainers agree this is real and worth doing.
Want to work on it? Comment to claim it. Check for an assigned person first.
status/help-wantedUp for grabs. Accepted, but not something maintainers are actively working on. Community contributions welcome — this is a great place to pick up work.
Comment to claim, then open a PR.
status/in-progressActive. Someone is working on this right now.
If you're the assignee, keep the issue updated. If not, check before starting duplicate work.
status/staleIdle. No activity for an extended period. Will be closed unless someone responds.
Comment if this is still relevant to you. Any activity resets the clock.
Priority Labels — How Urgent Is This?
Every accepted item gets exactly one priority label. Priority is based on user impact, not issue age or fix size.
priority/p0— CriticalUsers are losing data or can't use Gas City at all.
gc start,gc stop, rig setup) completely blockedThese get prioritized above all other work. PRs fixing p0 issues get fast-tracked.
Examples: data loss, rogue commits, all agents error on start.
priority/p1— HighA core workflow is broken, but Gas City is still usable overall.
Reviewed before lower-priority items. If your PR needs a rebase, we'll ask — the fix is worth getting current.
Examples: mail sent but never delivered, doctor reporting false positives on every run, complete hang on a supported platform.
priority/p2— MediumReal problem, but there's a workaround or it only affects uncommon setups.
This is where most day-to-day work lives. Bug fixes are reviewed before features at this tier.
Examples: config option ignored (workaround: set it elsewhere), misleading error output, wrong HTTP status code on an edge case.
priority/p3— BacklogGood idea, no current plan to build it. Community contributions welcome.
We review these when we can, and clean, well-tested PRs do get merged. If yours sits for a while, it's a reflection of our capacity, not your work.
Examples: new dashboard widget, structured --json output for scripting, support for an alternative service manager.
Kind Labels — What Type of Change Is This?
Kind labels are mutually exclusive — pick the one that best describes the primary intent.
kind/bugBroken behavior. Something that used to work (or should work per docs) doesn't.
kind/featureNew capability. Something that doesn't exist yet.
kind/docsDocumentation only. No code changes.
kind/choreInternal improvement. Refactoring, tests, CI, tooling, build system — anything that doesn't change user-visible behavior.
Filing guidance: "X doesn't work" →
kind/bug. "I wish X could do Y" →kind/feature. If your PR does both, label the primary intent. Don't overthink it — maintainers will adjust during triage.What This Means for Your Contribution
PRs that get merged fastest
status/acceptedorstatus/help-wantedissuemainPRs that get closed during triage
This Is a Volunteer Project
We don't make SLA guarantees. We aim to triage new issues within about a week, but it may take longer. If you see
status/needs-infoorstatus/needs-reproon your issue, please respond — issues without a response may be auto-closed after a period of silence so the tracker stays manageable.If you have questions about a label or want to discuss prioritization, comment on the issue or start a thread in this Discussion.
Beta Was this translation helpful? Give feedback.
All reactions