git-bug

Create a new identity

$ git bug user create

$ git bug add

$ git bug push

$ git bug pull

$ git bug ls

$ git bug ls "[status]:[open] [sort]:[edit]"

$ git bug ls "[search_query]" baz

git bug <subcommand> [<options>] [<arguments>]

list
    List all available bugs.

show
    Display detailed information for a specific bug by ID.

add
    Interactively create a new bug.

edit
    Modify the properties of an existing bug.

comment
    Add a new comment to a specified bug.

close
    Change the status of a bug to closed.

reopen
    Reopen a previously closed bug.

labels
    Add, remove, or list labels associated with a bug.

web
    Start a local web interface for browsing and managing bugs.

fetch
    Retrieve bug data from a remote Git repository.

push
    Publish local bug data to a remote Git repository.

git-bug is a distributed bug tracking system that stores its data directly within a Git repository. Unlike traditional centralized bug trackers (like Jira or Bugzilla), git-bug embraces Git's decentralized nature, allowing developers to track, create, edit, and comment on bugs offline.

Bug data, including descriptions, comments, and attachments, are stored as Git objects, enabling full version control, history, and synchronization through standard Git operations (push/pull). This architecture provides resilience against single points of failure and allows for a more fluid, branch-based workflow for managing issues, integrating seamlessly with existing Git repositories and workflows. It aims to make bug tracking as decentralized and version-controlled as source code itself.

• Decentralized Model: While powerful, the distributed nature can introduce complexity in conflict resolution for bug data, similar to code merges.
• Learning Curve: Requires familiarity with Git concepts beyond basic usage to fully leverage its distributed features.
• Data Storage: All bug data is stored in the Git repository, which can increase repository size, especially with many attachments.
• Ecosystem Maturity: As a relatively niche tool, its ecosystem (integrations, tooling) is not as mature as centralized solutions.

git-bug stores bug data as Git objects. When multiple users edit the same bug concurrently, merge conflicts can arise, requiring manual resolution similar to code conflicts.

Provides an optional, lightweight web interface for browsing and managing bugs, accessible via the git bug web command. This offers a more user-friendly view without external dependencies.

git-bug was initially created by Michael Brouwer (MichaelMure) to address the desire for a decentralized bug tracking system that seamlessly integrates with existing Git workflows. Development began around 2017-2018, aiming to overcome the limitations of centralized trackers by leveraging Git's core strengths: distribution, version control, and offline capabilities. Its design focuses on treating bugs as first-class Git objects, allowing them to be branched, merged, and pushed like code, thereby enabling a robust, collaborative, and resilient bug management process.

git(1), fossil(1)