3 ms·
I've been using GitHub Issues for this for the past few years, and I absolutely love it. Each of my projects has issues. If I'm fixing a bug or working on a fe
by simonw 5y ago
I've been using GitHub Issues for this for the past few years, and I absolutely love it.
Each of my projects has issues. If I'm fixing a bug or working on a feature I open an issue for it, then I post a stream of comments as I figure out the details, make decisions, find examples of code that I need to use and so on.
I have my own private notes repository which I just use for this for things that don't relate to a current project and that I don't want to publish yet.
I add a "research" label to my repos, and open research issues for ideas or for things that I want to explore that are relevant to the project in some way. Recent example: https://github.com/simonw/sqlite-utils/issues/344 https://github.com/simonw/sqlite-utils/issues/344 - researching STRICT mode that was just added to SQLite, and seeing if it would make sense to support it in my sqlite-utils library.
GitHub's issues API is comprehensive, so I have a cron that exports all of my issues and comments into a SQLite database that I can access with Datasette. I have a private one with all of my projects, and I also run a public one at https://github-to-sqlite.dogsheep.net/github/issues https://github-to-sqlite.dogsheep.net/github/issues with just the issues from my public Datasette-related projects.
I use search against these often. I occasionally even re-discover old notes from Google searches, which include the ones from my public repositories.
Many of my issues have dozens of comment replies, all from me. It's a great way of keeping a log.