The idea of hosting issues along with the repo seems intriguing. Does anyone have experience doing the same with git? Seems like some people are doing it:
It works with mercurial and git. I like the fact it's very simple and straightforward:
- Issues are maildirs in `.issues`, named with hashes
- The original description and subsequent comments are messages in those maildirs
- Metadata like status, severity, etc. are headers on the description message
There are simple commands to list, show, add and close issues. That's it.
If you want a UI to browse issues, just point any mail reader at `.issues`.
If you want a UI to input issues or comments, just set your EDITOR or VISUAL env var to either a text editor or an email editor (I use both: Emacs with `message-mode` ;) ).
If you want a Web UI, just use any maildir renderer (I use mhonarc).
If I recall correctly, having looked for such solutions in git a few years back, most of bug tracker management in a git repository project were either uncompleted or unmaintained.
some people use an org-mode file as issue list, but then non-developers cannot easily view or add issues to the list unless you set them up with an easy to use org-mode (web?) editor/viewer.
https://github.com/duplys/git-issues