Git-bug v0.11.0 releases with rebuilt web UI and data integrity fixes
Open-source distributed bug tracker embedded in Git ships major update with new web interface and improved data handling.
What to know
- Git-bug v0.11.0 ships with a rewritten web UI designed for actual issue work and a formal specification of its on-disk data format.
- The release fixes subtle data integrity bugs in the cache that could cause mismatches between stored and returned data, and now preserves unknown operations for forward compatibility.
- Author Michael Muré plans public portal access via OAuth, identity system rework with did:plc, and eventual pull request and CI support.
- Community discussion focuses on use cases for small teams, comparisons to other distributed trackers, and challenges in monetizing developer tools.
The dispute Whether the tool's reliance on Git and CLI interfaces is a strength for developers or a barrier to broader adoption. · positions read across 22 posts and comments
Distributed bug tracking in Git is conceptually elegant and well-suited for small teams working offline.
-
“Git has a wide open reference namespace for these kinds of ideas, and I'm always excited to see someone use it like this.”
AceJohnny2 · Hacker News ↗
The tool faces usability barriers for non-technical users and needs a clear path to monetization.
-
“Make it easy for non-technical users to also use this software. That will probably get you further along with gaining paid customers, IMO, because that's the hard part with something like this.”
ok_dad · Hacker News ↗
There are known technical issues and similar projects already exist that deserve consideration.
-
“I tried git-bug a few months ago, and [issue 1023] is a showstopper.”
jason_oster · Hacker News ↗
Michael Muré Git-bug creator and maintainerGit-bug project Open-source distributed bug tracker
How it unfolded 3 developments, newest first · click a bar or a number to jump articlespostscomments
-
3
Author outlines near-term roadmap including public portal and identity rework
Michael Muré, the project author, responds to community interest with plans for external authentication to enable public portal access, a git remote endpoint for the web UI, identity system rework using did:plc, and eventual support for pull requests and CI.
“have the webui accept external auth (like github oauth) so that it can be a public portal and accept external interactions…”
— michaelmure -
Git has a wide open reference namespace for these kinds of ideas, and I'm always excited to see someone use it like this.See, at core git is a collection of objects (referenced by their hash), along with references to tip-of-tree objects. These references are stored in the refs/ directory, and core git only uses a couple subdirs/namespaces under…
2 more of the top 3 · 22 posts in this stretch
-
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.htmlhttps://git.kernel.org/pub/scm/utils/b4/b4.git/bugs/https://kernel-recipes.org/en/2026/2026/09/22/live-blog-day-... (shameless…
-
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…
-
-
2
Git-bug reaches Hacker News front page and generates discussion
The project reaches 272 points on Hacker News with 91 comments, sparking discussion among developers about distributed bug tracking, design choices, and potential use cases. The author, Michael Muré, participates directly in comments sharing roadmap plans.
- 2 days quiet
-
1
Release addresses cache correctness bugs and data preservation
The v0.11.0 release resolves subtle but significant cache problems that could cause git-bug to return data not matching what was stored. Changes include preserving unknown operations so older binaries don't destroy unrecognized data, and publishing a formal specification of the on-disk format.
“Previously, reading and re-writing a bug with an older binary would quietly destroy anything it did not recognize. That made every future addition to the data model a compatibility hazard. It no longer is.”
— Git-bug release notes -
background
Git-bug releases v0.11.0 with rewritten web UI — After 16 months and nearly 300 commits since v0.10.1, git-bug v0.11.0 ships with a completely rebuilt web UI and significant data integrity improvements. The new web interface supports browsing, searching, filtering, and editing issues, as well as doubling as a code browser with file trees, syntax highlighting, and commit history.
Also covered reported alongside — the timeline has no entry for these yet
-
first by HN Best, 1d ago · also HN Frontpage
What people are saying 18 voices from 1 site · best of 22 · verbatim
- How does git-bug compare to other distributed bug trackers like Epiq and the tools discussed from a decade ago?
- What is the status of issue #1023 that was called a showstopper, and has it been resolved in v0.11.0?
- Can git-bug be extended to handle issues beyond bugs, such as general project management tasks?
- Yesterday
-
Call for people who severely dislike Jira to chip in $1 each, that should give you some runway.
-
I’ve been saying for years that issue tracking should just be done in git along with the rest of the code. I’ll definitely be checking this out.
-
Interesting approach. Curious how this compares to just using GitHub Issues for teams that are already git-centric — what's the main pain point this solves that Issues doesn't?
-
Can this be used for more than just bugs? I feel like it can but the name is going to be limiting.
-
> 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!Make it easy for non-technical users to also use this software. That will probably get you further along with gaining paid customers, IMO, because that's the hard part with something like this. It's easy for…
-
Awesome project. When I was using sourcehut, I have written a primitive script that lets you import issues into git-bug. Maybe it's useful to someone:
-
Stoked to see this.I've long felt that something like this was the way but have never gotten around to working on it.
-
Nice! I look forward to digging in to this.My own slightly-similar thing (uses an explicit sequence, and signed objects in refs/):
-
Thanks for posting! I don't see any mention of beads, which can also store the database in Git (via Dolt). How does this compare to it?
-
Thank you for working on this, I love the idea. What surprised me was the way user identities is managed, I assumed you’d use whatever git uses. Would you mind elaborating on that?
-
Offline-first bugs living next to the code is a nice fit for tiny teams. Less context switching than opening a separate tracker when you are just shipping a small project.
-
For your roadmap, it would help with collaborating and organizing to use the issue queueSomething like "scoped labels"
-
My favorite VCS friendly ticket tracker is https://github.com/wedow/ticketIt's human-readable, simple, and easy to work with. Basically there's no magic.
-
I tried git-bug a few months ago, and https://github.com/git-bug/git-bug/issues/1023 is a showstopper.There is a workaround, but it isn't pretty. You can push/pull bugs and identities with normal, ssh-agent-less git commands:
-
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…
-
You can also do code reviews in pure git:https://github.com/google/git-appraiseI used git bug before but found I missed being able to edit tickets with a Markdown editor. So I built this:
-
Just for those people for whom this might be a new concept: There is actually a fair number of these distributed bug trackers: <
-
A few months ago there was another of these posted, called Epiq: https://news.ycombinator.com/item?id=48155570My 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 (…