For early-stage SaaS and consumer startups.
Take 15 minutes to set up a basic issue tracking system (labels + milestones) you probably won’t have to think about for at least 6 months.
Want to create a fresh repo with these labels and milestones?
-
Click the green "Use this template" button.
-
To trigger the GitHub Action for the first time, edit the
name
field in.github/workflows/milestones.yml
to be"Use weekly Memorable Milestones"
. A small commit triggers the milestone syncing.
That's it! ⚡️
Want to use the labels and milestones for an existing repository?
-
Copy over the
.github/workflows/milestones.yml
file to your existing repository. You may have to create a.github
or.github/workflows
folder if you don't have one. (Files that end in.yml
in this folder are treated as GitHub Actions). -
To trigger the GitHub Action for the first time, edit the
name
field in.github/workflows/milestones.yml
to be"Use weekly Memorable Milestones"
. A small commit triggers the milestone syncing. -
Add the labels from this project to your repository manually. Unfortunately, this is currently the fastest way 🐢.
That's it! ⚡️
This will trigger actions that put your labels and milestones on auto-pilot.
The milestones are weekly sprints, created 7-8 weeks out, and due every Thursday. The GitHub Action will create them ahead of time and close them when they're done. Read the methodology.
The labels are a simple set of tags meant for private projects. Colors and names are determined to be memorable, simple, and accessible. Inspired by this research paper on colour theory.
Want to make it easy for members of your org to use this template when they create a new repo?
- Click the "Fork" button in the top right.
-
Choose which org you'd like to fork the repo to.
-
You're done!
When someone creates a new repo, this template will come up as an option.
Built with 💙 by the team behind Fabric.