Get Started
Open source that pays

Mission 5 of 6

Run your open source community without burning out.

After a launch comes the pile of issues and PRs that makes solo maintainers go silent or go rude. You'll set up rules you apply the same way every time, so you don't have to decide anything at 11pm.

55 minIntermediateFree toolsStep 1 free

What you'll do

Set up labels and weekly triage

Create seven labels that each mean one thing, then run a twenty minute weekly pass with a decision for every issue and PR.

Save your three most-used replies

Write the needs-repro, not-planned and changes-requested replies once, so your tone stays steady whatever your mood.

Grow contributors and spot burnout

Scope good first issues, set a release cadence and learn the warning signs before you snap.

  • A stale bot that only chases issues waiting on the reporter
  • Office hours that cost you one hour a month
Before you start
  • A repo with some issues and ideally a PR or two. If the launch was quiet, file three issues yourself from your own roadmap; the system is the same
  • gh logged in with access to the repo
  • An honest number for how many hours a week you want to give this. Write it down; step 6 uses it
Your progress0/6
01/06Labels that mean something0 done
STEP 01 of 06~8 min

Labels that mean something

Replace GitHub's decorative defaults with a small set where each label is a state, so the tracker tells you what to do next.

The launch worked, and now there are forty open issues and a notification sound you've started to dread. The fix is not more hours. It's a small set of rules you apply the same way every time, and labels are the first of them.

Labels as states

GitHub's default labels (enhancement, help wanted, question, invalid, wontfix) describe what an issue is. That's not useful.

You want labels that describe where it is in your process, so filtering by label gives you a to-do list. Seven is enough:

  • triage: nobody has looked yet. Every new issue gets this automatically via the template from mission 2.
  • needs-repro: you looked, couldn't reproduce, asked for more. The ball is with the reporter.
  • bug: you reproduced it. The ball is with you.
  • feature: agreed and wanted, not built. Anyone can pick it up.
  • good first issue: a feature or bug you've scoped with pointers, for a newcomer. GitHub surfaces this label on its contribute page and in search.
  • blocked: waiting on an upstream fix or a decision outside the repo.
  • not-planned: closed on purpose, with a reason. Lets you find your past decisions when the same request comes back.

Create them with one script

  1. Run this in bash or Git Bash. It deletes the defaults you won't use, creates the seven labels, then lists them:

    Terminal (bash or Git Bash)
    # Delete the GitHub defaults you won't use, then create a small set with meaning
    for l in "help wanted" "invalid" "question" "wontfix" "documentation" "enhancement"; do
      gh label delete "$l" --yes 2>/dev/null
    done
    
    gh label create "triage"            --color E4E669 --description "Not yet looked at by a maintainer" --force
    gh label create "bug"               --color D73A4A --description "Confirmed: reproduced by a maintainer" --force
    gh label create "needs-repro"       --color FBCA04 --description "Waiting on a reproduction from the reporter" --force
    gh label create "feature"           --color 0E8A16 --description "Agreed feature, not yet built" --force
    gh label create "good first issue"  --color 7057FF --description "Scoped, with pointers, for a new contributor" --force
    gh label create "blocked"           --color 000000 --description "Waiting on something outside this repo" --force
    gh label create "not-planned"       --color FFFFFF --description "Closed on purpose; see the comment" --force
    
    gh label list

Your actual to-do list

Two filters do the work: is:open label:triage and is:open label:bug. Everything else is either someone else's turn or already decided.

  1. Bookmark both filters.

    Tip
    Add labels: [triage] to the bug template from mission 2 if it isn't there, and labels: [feature, triage] to a feature template if you make one. Then you never label by hand on arrival.
Checkpoint
gh label list shows exactly your set, and gh issue list --label triage returns the issues nobody has looked at. That list is the input for the next step.
If it breaksDeleting the defaults fails on labels in use
Deleting the defaults fails on labels in use
gh label delete removes the label from issues too; it fails only if the name doesn't exist, which the 2>/dev/null hides. If you'd rather keep history, rename instead: gh label edit enhancement --name feature.
Still stuck? Ask the community
Next mission · Open source that paysMake it pay: pick the money model that fits your licence and your users
→