Git-bug puts your issue tracker inside the repo — distributed and offline

Git-bug is a bug tracker that lives entirely inside a Git repository, storing issues as objects in Git itself rather than as files that clutter your project tree. Because the data rides along with your existing remotes, developers push and pull bugs the same way they move code, collaborate without a central server, and keep reading and writing issues while completely offline. Listing or opening a bug takes milliseconds, and since every clone holds the full history, an outage or shutdown of a hosted tracker no longer means losing access to your issues.

The tool ships several interfaces from a single Go binary: a CLI, an interactive terminal UI, and a local web UI that also works as a lightweight code browser with syntax highlighting, commit history, and diffs. The web front end talks to the backend over a GraphQL API, making git-bug scriptable and easy to wire into editors or other tooling. Bridges let it import from and export to GitHub, GitLab, Jira, and Launchpad, so it can serve as a fast local mirror of an existing tracker rather than a full replacement.

The project’s on-disk layout — a DAG-based entity format covering identities and bugs — is formally specified, inviting alternative implementations and third-party tools that read the data directly. A planned public-portal web UI with external OAuth is still a work in progress, which is the main gap for teams that need to accept issue reports from anonymous users. Released under GPLv3, git-bug is a notable example of treating Git as a general-purpose distributed datastore rather than just a code host.