This interview with Simon Willison is great.

It finally1 pushed me into using GitHub Issues for my private repositories. They’re wonderful. (In the past, I’ve been just tracking everything in Markdown. That worked, but was just OK.)

As an example, I maintain a private GitHub repo with notes and documents for a private network I maintain on a volunteer basis.

It’s very ad-hoc and I sometimes go months between without working on it, so I didn’t want to clutter up my personal TODO list with tasks related to it.

Issues have been a wonderful way to track the various tasks I need to do as part of that role. They keep everything organized in a self-contained space.


  1. I know I’m late to this party. You may wonder how I’ve been a paying customer of GitHub for 10 years without using Issues. That’s because the overwhelming majority of my software development is done on non-GitHub repos hosted internally to my company. ↩︎