Yet another Hacker News

Git-bug: Distributed, offline-first bug tracker embedded in Git

88 points alentred 2 hours ago 20 comments

bonjune 1 hour ago | parent

Looks like GitHub issue tracker is embedded in git itself. Interesting!

Lucasoato 4 minutes ago | parent

Who knows how many things GitHub does are actually embedded into git itself :)

lolakutty 1 hour ago | parent

Someone is taking lessons from fossil-scm.

Looks great by the way.

bflesch 1 hour ago | parent

Looks really nice, I wonder why there hasn't been a project with this exact name and functionality before. When I think about it, "git bug" is quite limiting (the bug vs. feature discussion).

Naming things is hard, but I can see that it might feel unnatural to use "git bug" to track features. Maybe that's totally okay because it does one thing - tracking bugs - very well, and the whole feature roadmap is living in another system/process anyways?

dizhn 1 hour ago | parent

Their logo is a ladybug so everything works out in the end.

Towaway69 1 hour ago | parent

Isn't everything nowadays a bug?

Only once it gets fixed does it become a feature.

;)

sodapopcan 46 minutes ago | parent

Although if it doesn't get fixed, it also sometimes becomes a feature.

Meneth 1 hour ago | parent

Bugzilla has been using the term "bug" to track features for nearly 3 decades now. Doesn't seem to hamper them.

michaelmure 30 minutes ago | parent

I do want to extend to pull-request and more, so I'll need to at least make space in the CLI commands. Having a "git bug bug" next to a "git bug pr" is quite ugly.

Naming is hard, but I mostly didn't expect to reach that point :-)

Aissen 1 hour ago | parent

b4 maintainer and Director of LF IT Konstantin Ryabitsev demo-ed git-bug support in b4 and cgit (kernel.org fork) just this week at the Kernel Recipes conference:

https://b4.docs.kernel.org/en/latest/maintainer/bugs.html

https://git.kernel.org/pub/scm/utils/b4/b4.git/bugs/

https://kernel-recipes.org/en/2026/2026/09/22/live-blog-day-... (shameless plug)

mcepl 11 minutes ago | parent

Wow! Was this sent upstream to cgit?

saadn92 59 minutes ago | parent

excellent! will definitely give this a try

Izkata 59 minutes ago | parent

A few months ago there was another of these posted, called Epiq: https://news.ycombinator.com/item?id=48155570

My comment on there is about a surge in popularity of these over a decade ago, with a link to a previous comment about problems I remember them having that prevented them from being usable for most people ( https://news.ycombinator.com/item?id=47956979 ), because of their intended design rather than an implementation issue. For example bullet 3 was a problem in one, that another tried to solve with bullet 2.

I don't have time right now to look at this one to guess if these apply, but might be interesting/useful for someone else.

lelanthran 43 minutes ago | parent

Other than the first bullet point in your list[1], my contribution in this regard addresses everything else.

Don't have a link handy but it's on github called "rotsit" (revenge of the something issue Tracker).

‐----‐------

[1] That's the entire point of having the issue tied to a branch: if an issue is marked resolved in the branch you are looking at, then its resolved in the branch you are looking at. Storing the issues independent of branch means you need to also store extra metadat about which branch it is broken on.

teddyh 45 minutes ago | parent

Just for those people for whom this might be a new concept: There is actually a fair number of these distributed bug trackers: <https://news.ycombinator.com/item?id=22833037>

mcepl 12 minutes ago | parent

And none of them actually work really well. This blog post is over ten years old, but the situation didn’t improve much https://matej.ceplovi.cz/blog/current-state-of-the-distribut...

michaelmure 38 minutes ago | parent

Hi, author here, nice to see some interest :-)

FYI, this is my near-term roadmap:

  - have the webui accept external auth (like github oauth) so that it can be a public portal and accept external interactions
  - have the webui expose a git remote endpoint
  - slightly rework identities (and likely root them in did:plc for pubkey distribution, the identity system from bluesky, without being an ATProto thing), which would allow to share identities between repos way more naturally
  - extend to support pull-requests, possibly CI. That would make it a somewhat complete local-first forge that you can also self-host trivially

Also, while there is some attention ... I'm considering working on this full time. If you have some advice or opportunities on how I can support myself doing this, let me know!

delf 27 minutes ago | parent

Git-bug looks amazing! Author of GitSocial here, would love to hear your opinion:

https://gitsocial.org/

sebiw 24 minutes ago | parent

First of all: Huge respect for getting something out the door, looks really useful.

> I'm considering working on this full time. If you have some advice or opportunities on how I can support myself doing this, let me know!

You could consider an "enterprise" tier with a special subset of features and guaranteed support. But my experience tells me this will be really hard to substantially monetize, as the customer profile for that solution is probably not spending on software until they really need to (the saying goes: selling to developers is impossible, you need to sell to their boss). Maybe a donation model or a creator-centric thing could work out!

imagent 24 minutes ago | parent

You can also do code reviews in pure git:

https://github.com/google/git-appraise

I used git bug before but found I missed being able to edit tickets with a Markdown editor. So I built this: https://github.com/LoumTechnologies/ticketry