>_ hackerrepos search repos…

← top repos

git-bug/git-bug

Distributed, offline-first bug tracker integrated in git

▲ 11 hackers recommend 2 strongly Go ★ 11k GPL-3.0 bugtrackerdecentralized-applicationdistributed-systemsgitgitdb

Recommended between 2025-10-11 and 2026-09-25. Last pushed 2026-11-01.

▲ 11 recommend · ▼ 1 criticism

What hackers say

“I've used git-bug[1] for issues and it works pretty well.”

— paularmstrong, 2026-08-17 · strong recommendation · original comment on Hacker News ↗

show original comment

I've used git-bug[1] for issues and it works pretty well. The web-ui is lagging behind and PR support would be everything you'd need to ditch a central-hosted web instance. [1] https://github.com/git-bug/git-bug

“I would love to see more projects use git-bug, which works very well for offline collaboration.”

— iamnothere, 2025-11-30 · strong recommendation · original comment on Hacker News ↗

show original comment

I would love to see more projects use git-bug, which works very well for offline collaboration. All bug tracker info is stored in the repo itself. https://github.com/git-bug/git-bug It still needs work to match the capabilities of most source forges, but for small closed teams it already works very well.

“I have had my eye on these technologies for a while. Embedding the issue tracker and such in your git repo.”

— dannyfritz07, 2026-04-28 · original comment on Hacker News ↗

show original comment

I have had my eye on these technologies for a while. Embedding the issue tracker and such in your git repo. Every day these make more and more sense. - https://gitsocial.org/ - https://radicle.dev/ - https://github.com/git-bug/git-bug

“A suggestion: use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg.”

— nextaccountic, 2026-04-28 · original comment on Hacker News ↗

show original comment

> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc. A suggestion: use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg. It saves issues, PRs etc in git itself (not on a branch - on a specially crafted ref). It offers two way sync with a lot of providers. Other VCSes like fossil store issues alongside the repo. I think it's appropriate because in a sense, issues are part of what gives meaning to the code (like documentation)

“https://github.com/git-bug/git-bug if that's your thing.”

— michaelmure, 2026-04-09 · original comment on Hacker News ↗

“git-bug[1] looks promising, but I haven't tried it.”

— GalaxySnail, 2026-03-26 · original comment on Hacker News ↗

show original comment

git-bug[1] looks promising, but I haven't tried it. [1] https://github.com/git-bug/git-bug

“Haven't used it, but I've been intrigued by git-bug (stores issues in got itself) for years, to use as the issue/pr sync.”

— patcon, 2026-03-23 · original comment on Hacker News ↗

show original comment

Haven't used it, but I've been intrigued by git-bug (stores issues in got itself) for years, to use as the issue/pr sync. Bonus that now the issues aren't vendor locked either https://github.com/git-bug/git-bug/blob/trunk/doc/feature-matrix.md

“Have you looked at https://github.com/git-bug/git-bug ?”

— hunvreus, 2026-02-24 · original comment on Hacker News ↗

“I would love git-bug project[1] to be successful in achieving that.”

— okanat, 2026-02-17 · original comment on Hacker News ↗

show original comment

I would love git-bug project[1] to be successful in achieving that. That way Git forges are just nice Web porcelain on top of very easy to migrate data. [1] https://github.com/git-bug/git-bug

“maybe of interest: https://github.com/git-bug/git-bug”

— khimaros, 2025-11-05 · original comment on Hacker News ↗

Criticism

“I tried git-bug a few months ago, and https://github.com/git-bug/git-bug/issues/1023 is a showstopper.”

— jason_oster, 2026-09-25 · original comment on Hacker News ↗

show original comment

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: https://gist.github.com/parasyte/80ef925d4b01216f6bcb051356faffb9

Badge for your README

hackers recommend badge
[![hackers recommend](https://hackerrepos.org/badge/git-bug/git-bug.svg)](https://hackerrepos.org/repo/git-bug/git-bug)