What does HackerNews think of git-bug?

Distributed, offline-first bug tracker embedded in git, with bridges

Language: Go

As a sort of spiritual successor to git-appraise, I've been working on git-bug[1] which support issues and will at some point support kanban and code review. There is a few notables improvements:

- CRDT-like reusable data structure [2][3] for true p2p workflow and easily create new entities (code review ...)

- bidirectional bridges to github, gitlab ... to ease the transition or just use git-bug as a complement of those platform

- CLI, terminal UI and web UI, for different taste and integrate into your tooling/workflow

[1]: https://github.com/MichaelMure/git-bug

[2]: https://github.com/MichaelMure/git-bug/blob/master/doc/model...

[3]: https://github.com/MichaelMure/git-bug/blob/master/entity/da...

Regarding the issues, there are some projects like git-bug https://github.com/MichaelMure/git-bug trying to embed these sorts of meta-work into git.
If that makes you mad, I still need help with https://github.com/MichaelMure/git-bug ;-) Coming at some point, kanban and pull-request support, offline-first!
Use git-bug. It never goes down, is about as private as possible, and the issue tracker UI is actually really pleasant. https://github.com/MichaelMure/git-bug
https://github.com/MichaelMure/git-bug

Offline-first bug tracker (and soon-ish forge) embedded in git.

I keep working on this because the idea makes a lot of sense to me, because I learn a lot from it and it benefits me indirectly.

I'm not especially looking to monetize, but I'm curious about what this community think about it.

Really cool. I have with git-bug[0] similar properties (offline first, identities, generic "crdt like" base data structure... ). Maybe you'd like to have a look and improve each other's design.

[0]: https://github.com/MichaelMure/git-bug

in the end the author states "So, for now: git notes are relegated to obscurity. Forever hamstrung by an obscure and clunky interface and limited adoption—I often forget they’re there.", so after the read, I should forgot about it?

git does need a 'git bug' to track bugs though, as https://github.com/MichaelMure/git-bug does, but I prefer to have it built in git directly if possible.

There is also git-bug [1], an offline bug tracker fully embedded in git which can bridge to Github, Gitlab, Jira

[1] https://github.com/MichaelMure/git-bug

You can already store and sync issues in git repo metadata, check out git-bug: https://github.com/MichaelMure/git-bug
Hi everyone. I'd like to show you the result of a long maturation process, the reusable distributed data structure of git-bug, that you can use in your own project to store your entities in git and collaborate through git remotes.

I'm hoping that this could spawn a new kind of developer tools, where all the "metadata" (bugs, kanban ...) of a project are stored and shipped alongside the code, always available offline, integrated in our tool of choice and always snappy.

If you have experience in that domain, please pock holes in it. There is always tradeoffs, but I'm hoping to avoid fundamental flaws.

In the mean time, git-bug[0] itself is close to a 1.0 release. This Show HN is a step in making sure the data model is correct and strong. Thank you!

[0]: https://github.com/MichaelMure/git-bug

Do you fancy re-thinking buf trackers? I'm looking for help over at https://github.com/MichaelMure/git-bug to create a distributed bug tracker embeded in git, with bridges.

It's close to be ready for prime time, yet there is so much that could be done to make it better.