This looks awesome, but will switching branches or reverting commits in the repo affect the history of my git-bug issues?
Git-bug: Distributed, offline-first bug tracker embedded in Git
21–30 of 82 posts
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#22This looks awesome, but will switching branches or reverting commits in the repo affect the history of my git-bug issues?
No, it's completely separated from your normal code and branches and doesn't pollute your development workflow. git-bug's data is stored in hidden branches (not in the way you think about branches though).
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#23There are a number of tools for distributed bug tracking: https://news.ycombinator.com/item?id=22833037
I personally use https://mrzv.org/software/artemis since it's very lightweight, agnostic about VCS, and stores issues in a standard format (maildir) with existing tooling for reading, writing and other processing (e.g. Emacs to read/write, and MHonArc to build into a Web site)
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#24This is a great project! git bug really should be a built-in subcommand for git.
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#25I want it.
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#26I also like the write up about its internal data structure. It really helped me understand how to build my own git based tools.
So thanks for that!
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#27I also like the write up about its internal data structure. It really helped me understand how to build my own git based tools. So thanks for that!
As mentioned in the release notes, the intent is really to have a reusable data structure in git capable of conflict resolution, plus all the tooling around that. So if you want to build a tool using the same techniques but outside of git-bug's scope, please consider using it as a library.
Re: Git-bug: Distributed, offline-first bug tracker embedded in Git
#28I understand why the bug IDs are hashes, but that's going to be pretty inconvenient for practical use. Yes I know we manage it with Git commit names, but bug IDs are printed and spoken much more than commits, e.g. when communicating with a test team, management, or even in release notes.
I wonder if we could use some sort of distributed naming scheme for this, similar to Blockchain DNS?