{"slug": "git-bug", "name": "git-bug", "category": "productivity", "category_name": "Productivity", "description": "", "recommenders": 3, "commenters": 5, "warners": 1, "score": 1.458, "rising": 0.35, "first": "2026-04-28", "latest": "2026-10-30", "why": "use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 2, "compare": 0, "warn": 1}, "spark": [0, 0, 0, 0, 0, 2, 0, 0, 0, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg.", "icon": true, "domain": null, "github_repo": "github.com/git-bug/git-bug", "official_url": "https://github.com/git-bug/git-bug", "pricing": "", "aliases": ["git-bug"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 789328048, "item_id": 49333003, "url": "https://news.ycombinator.com/item?id=49333003", "by": "paularmstrong", "date": "2026-08-17", "stance": "recommend", "quote": "I've used git-bug[1] for issues and it works pretty well.", "excerpt": "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", "context": "", "use_case": "issue tracking in git", "switched_from": "", "story": "Ask HN: Alternatives to GitHub"}, {"id": 767043920, "item_id": 47940245, "url": "https://news.ycombinator.com/item?id=47940245", "by": "stryan", "date": "2026-04-28", "stance": "recommend", "quote": "git-bug is great but it doesn't handle PRs", "excerpt": "git-bug is great but it doesn't handle PRs nor does it have a method for users without commit rights to submit bugs to the project. I know they're working on the latter (something with the web UI?) but until then you still need some kind of public infra for issue management if you want the general public to be able to submit issues. I use it for my project[0] to keep issues centralized with the repo, but I still use ", "context": "uses it for their own project", "use_case": "issue tracking inside the repo", "switched_from": "", "story": "Ghostty is leaving GitHub"}, {"id": 767038720, "item_id": 47939920, "url": "https://news.ycombinator.com/item?id=47939920", "by": "nextaccountic", "date": "2026-04-28", "stance": "recommend", "quote": "use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg.", "excerpt": "> 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 issue", "context": "", "use_case": "storing issues and PRs in git", "switched_from": "", "story": "Ghostty is leaving GitHub"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 797541568, "item_id": 49846348, "url": "https://news.ycombinator.com/item?id=49846348", "by": "jason_oster", "date": "2026-09-25", "stance": "warn", "quote": "I tried git-bug a few months ago, and https://github.com/git-bug/git-bug/issues/1023 is a showstopper.", "excerpt": "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", "context": "", "use_case": "bug tracking in Git", "switched_from": "", "story": "Git-bug: Distributed, offline-first bug tracker embedded in Git"}]}], "who": [{"by": "stryan", "context": "uses it for their own project", "url": "https://news.ycombinator.com/item?id=47940245", "date": "2026-04-28"}], "tags": [], "use_cases": ["issue syncing", "bug tracking in git", "bug tracking", "issue tracking in git", "issue tracking inside the repo", "storing issues and prs in git"], "compared": [], "makers": [{"id": 789344336, "item_id": 49334021, "url": "https://news.ycombinator.com/item?id=49334021", "by": "michaelmure", "date": "2026-08-17", "stance": "neutral", "quote": "I have a new and much better webui that I need to release.", "excerpt": "FWIW, I have a new and much better webui that I need to release. I'm also planning to work on PRs and other stuff around the end of the year.", "context": "", "use_case": "issue tracking in git", "switched_from": "", "story": "Ask HN: Alternatives to GitHub"}], "threads": [{"url": "https://news.ycombinator.com/item?id=49843174", "title": "Git-bug: Distributed, offline-first bug tracker embedded in Git", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49331033", "title": "Ask HN: Alternatives to GitHub", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=47939579", "title": "Ghostty is leaving GitHub", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50305573", "title": "The federated code forge", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 2}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {"neutral": 1, "warn": 1}, "2026-10": {"neutral": 1}}, "quotes": [{"id": 804907763, "item_id": 50306735, "url": "https://news.ycombinator.com/item?id=50306735", "by": "stryan", "date": "2026-10-30", "stance": "neutral", "quote": "Just need git-bug to add a Tangled bridge so I can keep issues synced", "excerpt": "Really looking forward to seeing Tangled develop! I've got a side project that's main repo and CI is on my self-hosted Gitea but code and releases are mirrored to Github; I'm hoping to move it off Gitea and onto Tangled for code/releases/potentially CI and just keep Github for discoverability/backups/namespace \"squatting\". Just need git-bug to add a Tangled bridge so I can keep issues synced and (ideally) for there t", "context": "", "use_case": "issue syncing", "switched_from": "", "story": "The federated code forge"}, {"id": 797541568, "item_id": 49846348, "url": "https://news.ycombinator.com/item?id=49846348", "by": "jason_oster", "date": "2026-09-25", "stance": "warn", "quote": "I tried git-bug a few months ago, and https://github.com/git-bug/git-bug/issues/1023 is a showstopper.", "excerpt": "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", "context": "", "use_case": "bug tracking in Git", "switched_from": "", "story": "Git-bug: Distributed, offline-first bug tracker embedded in Git"}, {"id": 797514865, "item_id": 49844679, "url": "https://news.ycombinator.com/item?id=49844679", "by": "imagent", "date": "2026-09-25", "stance": "neutral", "quote": "I used git bug before but found I missed being able to edit tickets with a Markdown editor.", "excerpt": "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", "context": "", "use_case": "bug tracking", "switched_from": "", "story": "Git-bug: Distributed, offline-first bug tracker embedded in Git"}, {"id": 789328048, "item_id": 49333003, "url": "https://news.ycombinator.com/item?id=49333003", "by": "paularmstrong", "date": "2026-08-17", "stance": "recommend", "quote": "I've used git-bug[1] for issues and it works pretty well.", "excerpt": "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", "context": "", "use_case": "issue tracking in git", "switched_from": "", "story": "Ask HN: Alternatives to GitHub"}, {"id": 767043920, "item_id": 47940245, "url": "https://news.ycombinator.com/item?id=47940245", "by": "stryan", "date": "2026-04-28", "stance": "recommend", "quote": "git-bug is great but it doesn't handle PRs", "excerpt": "git-bug is great but it doesn't handle PRs nor does it have a method for users without commit rights to submit bugs to the project. I know they're working on the latter (something with the web UI?) but until then you still need some kind of public infra for issue management if you want the general public to be able to submit issues. I use it for my project[0] to keep issues centralized with the repo, but I still use ", "context": "uses it for their own project", "use_case": "issue tracking inside the repo", "switched_from": "", "story": "Ghostty is leaving GitHub"}, {"id": 767038720, "item_id": 47939920, "url": "https://news.ycombinator.com/item?id=47939920", "by": "nextaccountic", "date": "2026-04-28", "stance": "recommend", "quote": "use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg.", "excerpt": "> 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 issue", "context": "", "use_case": "storing issues and PRs in git", "switched_from": "", "story": "Ghostty is leaving GitHub"}]}