GitHub Labels, Milestones and Issue Triage Process
Design a triage routine that keeps issues under control.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design an issue triage process for [PROJECT]. Volume of new issues: [VOLUME]. Maintainers and time available: [MAINTAINERS]. Types of issue: [ISSUE_TYPES]. Release plan: [RELEASE_PLAN]. Provide a label table (name, colour hex, description, when to use it, who may apply it) with fewer than 20 labels across type, priority, status and area, with consistent colours (for example red for bugs, blue for features), plus milestone use. Describe the weekly triage steps for each new issue (reproduce, label, ask for information, assign, close as duplicate or not planned), response time targets, and a 30-minute meeting agenda in minutes that add up. Write four message templates in full: needs-info, duplicate, won't fix and welcome. Define stale rules with a kind warning before closing, and treat security-related issues separately and privately. Worked triage of three invented issues: a bug report missing steps (needs-info, reply with the template), a duplicate (link and close), and a feature request (enhancement label, added to the discussion backlog, with an explanation of how requests are prioritised). Track two or three numbers: median days to first response and open issues older than 90 days; for example 24 new issues with 20 triaged within two days is 83 percent. Avoid process that costs more than it saves.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.