Like many other Open Source projects, restic uses GitHub for hosting the source code and managing issues. Over time, we discovered that oftentimes users open an issue on GitHub which just consists of a question, for example on how to use restic in a certain situation. While such issues can be answered quickly, sometimes there’s no consent on when the issue can be seen as resolved and therefore closed (the issue is not actionable). The GitHub issue tracker is then cluttered with issues for which there is no clear next action and no clear “resolved” state. This blog post describes how we set up the issue templates on GitHub to resolve this situation nicely.
This is a companion discussion topic for the original entry at https://restic.net/blog/2018-09-09/GitHub-issue-templates