How we organize GitHub issues: A simple styleguide for tagging

For people who make software, the internet has no shortage of best practice for workflow organization like Git Flow, release versioning, GitHub, etc. When you get to the topic of issue management, the reading material plummets.

At Robin, GitHub issues are the core of just about every action the team takes. Over the past year, we’ve worked out an internal tagging system that keeps engineering and product efforts organized across repositories on Github. We’re sharing the current iteration (and it will keep changing) in case your team is looking for some workflow inspiration.

Styleguide for issue tagging

Label Groups

We group labels by color, according to broad themes. Labels are consistent across repositories, except for a few language specific topics. This makes switching between projects easy, since you don’t need domain expertise in order to write an issue. New team members can learn the system once, and use it everywhere.

Platform

If the repository covers multiple parts, this is how we designate where the issue lives. (i.e. iOS and Android for cross-platform tablet app).

Problems

Issues that make the product feel broken. High priority, especially if its present in production.

Related

The sweet spot for employee engagement lies somewhere in the balance between boredom and overwhelm. What gets in the way? Many people find themselves stuck on one side due to clutter of meeting-packed work days.