I wrote my own: https://git.dillo-browser.org/buggy/ https://git.dillo-browser.org/buggy/ It fetches the issues from GitHub and stores them in <number>/index.

I wrote my own: https://git.dillo-browser.org/buggy/ https://git.dillo-browser.org/buggy/ It fetches the issues from GitHub and stores them in <number>/index.md in Markdown format, with some special headers. I then keep the issues in a git repository: https://git.dillo-browser.org/bugtracker/ https://git.dillo-browser.org/bugtracker/ So we have a very robust storage that we can move around and also allows me to work offline. When I want to push changes, I just push them via git, then buggy(1) runs in the server via a web hook. This also tracks the edit changes. While typing, I often use `find . -name '*.md' | entr make` which regenerates the issues that have changed into HTML as well as the index, then sends a SIGUSR1 to dillo, which reloads the issue page. The nice thing of allowing arbitrary HTML inline is that I can write the reproducers in the issue itself: https://git.dillo-browser.org/bugtracker/tree/501/index.md#n23 https://git.dillo-browser.org/bugtracker/tree/501/index.md#n... Closing an issue is just changing the header "State: open" by "State: closed", often with a comment pointing to the merged commit.