Git-bug is a bug tracker that stores issues directly inside a git repository's object graph — not as files in your working tree, but as native git data structures. The result is a fully distributed, offline-capable issue tracker that travels wherever your repo goes. Push and pull bugs the same way you push and pull code. No server required, no SaaS subscription, no vendor lock-in. The tool ships as a single Go binary that bundles a CLI, an interactive terminal UI, and a full web UI with syntax-highlighted code browsing, commit history, and a GraphQL API backend. Users can create identities, file bugs, comment, label, and change status through whichever interface suits them. The CLI supports query-based filtering and sorting, making it scriptable and composable with existing developer tooling. Bridge support is the pragmatic concession to reality: git-bug can import from and export to GitHub, GitLab, Jira, and Launchpad. This means teams don't have to abandon existing workflows to adopt it. You can use git-bug as a local offline interface to a centralized tracker, syncing bidirectionally when connectivity allows. The bridge architecture acknowledges that pure decentralization rarely wins adoption battles — interoperability does. The data model is formally specified in an open spec covering DAG entity format, identities, and the bug entity. This is not an afterthought; it's an invitation for alternative implementations and third-party tooling. The project is GPLv3-licensed, community-funded through backers and sponsors, and accepts contributions through a documented development workflow. The architecture avoids polluting the project's file tree entirely. Bugs live in git's object store, which means they don't show up in diffs, don't conflict with code changes, and don't bloat the working directory. This is a clean separation that most file-based alternatives (plain text issue trackers stored as markdown files) cannot match. The planned roadmap includes a public-facing web UI with OAuth authentication, which would allow open-source projects to accept external bug reports without requiring contributors to install anything. This is the missing piece for broader adoption — without it, git-bug remains a power-user tool for teams that already share git remotes. The project also lists 'inflatable raptor' as a planned feature, which suggests the maintainers have a sense of humor about roadmap documents. The core value proposition is structural: by collapsing the bug tracker into the version control system, git-bug eliminates an entire category of infrastructure dependency. If GitHub goes down, your issues are still local. If you switch hosting providers, your issue history migrates with a git push. This is generative infrastructure — it creates capability without extracting rent.
