Author outlines near-term roadmap including public portal and identity rework
3 Yesterday 9:36 AM · 1d ago · 1 post · 18 comments · 2 sources · development 3 of 3
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”
michaelmureMichael Muré Git-bug creator and maintainerGit-bug project Open-source distributed bug tracker
The whole story articlespostscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 22 voices · verbatim
-
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…
-
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…
-
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 (…
-
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…
-
> - have the webui accept external auth (like github oauth) so that it can be a public portal and accept external interactionsHave you looked into ForgeFed? It's a WIP plan for different Forgejo based forges to federate with each other. https://forgefed.org/There's also this: https://indieauth.net/ though I haven't looked into it. I hope you could…
-
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:
-
> 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…
-
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:
-
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:
-
For your roadmap, it would help with collaborating and organizing to use the issue queueSomething like "scoped labels"
-
Nice! I look forward to digging in to this.My own slightly-similar thing (uses an explicit sequence, and signed objects in refs/):
-
Just for those people for whom this might be a new concept: There is actually a fair number of these distributed bug trackers: <
-
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.
-
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?
-
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.
-
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.
-
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?
-
Stoked to see this.I've long felt that something like this was the way but have never gotten around to working on it.
-
Can this be used for more than just bugs? I feel like it can but the name is going to be limiting.
-
Call for people who severely dislike Jira to chip in $1 each, that should give you some runway.
All 3 developments of Git-bug v0.11.0 releases with rebuilt web UI and data… →
Hacker NewsNewswiresMastodon