// HACKER NEWS — CYBERSECURITY
Git-bug: Distributed, offline-first bug tracker embedded in Git
See INSTALLATION.md for the complete guide, including how to build from source and verify your install.
There are multiple ways to use git-bug. See the workflow documentation for the details.
This is the pure git-bug experience. In a similar fashion as with code, use git bug push and git bug pull to push and pull your bugs between git remotes and collaborate with your teammate.
As git-bug has bridges with other bug-trackers, you can use it as your personal local remote interface. Sync with git bug bridge pull and git bug bridge push, work from your terminal, integrate into your editor, it's up to you. And it works offline!
Often, projects need to have their bug-tracker public and accept editions from anyone facing a problem. To support this workflow, git-bug aims to have the web UI accept external OAuth authentication and act as a public portal. However the web UI is not up to speed for that yet. Contributions are very much welcome!
Your favorite editor will open to write a title and a message.
You can now use commands like show, comment, open or close to display and modify bugs. For more details about each command, you can run git bug --help or read the command's documentation.
An interactive terminal UI is available using the command git bug termui to browse and edit bugs.
You can launch a rich Web UI with git bug webui. Browse, search and filter issues, open new ones, comment, and edit titles, labels and status. It also doubles as a code browser for your repository, with a file tree, syntax-highlighted files, commit history and diffs.
The web UI is packed inside the same go binary and served by a local http server. It talks to the backend through a GraphQL API, whose schema is available here.