Distributed, offline-first bug tracker embedded in git, with bridges
Go to file
2018-09-06 21:42:05 +02:00
bug bug: also update the operations incrementaly in the snapshot 2018-09-04 20:06:26 +02:00
cache cache: fix missed code path that should update the cache 2018-09-04 18:20:21 +02:00
commands cmds: various cleaning 2018-09-06 21:42:05 +02:00
doc cmds: various cleaning 2018-09-06 21:42:05 +02:00
graphql cache: provide a generic bug sorting function 2018-09-02 16:36:48 +02:00
input cleanup go imports 2018-08-13 18:39:19 +02:00
misc random bugs: cleanup + generate random OperationPack as well 2018-09-06 14:11:10 +02:00
repository cmds: various cleaning 2018-09-06 21:42:05 +02:00
termui cache: provide a generic bug sorting function 2018-09-02 16:36:48 +02:00
tests random bugs: cleanup + generate random OperationPack as well 2018-09-06 14:11:10 +02:00
util cache: lock the repo with a pid file; automatic cleaning 2018-08-21 19:13:08 +02:00
vendor add a new main to generate random bugs 2018-08-16 18:22:00 +02:00
webui invert the behavior of the build flag for the webui 2018-09-02 00:06:50 +02:00
.gitignore upgrade the readme 2018-08-06 03:26:42 +02:00
.travis.yml webui: Ensure code format in CI by running eslint 2018-08-19 23:14:45 +02:00
git-bug.go webui: pack the files only on demand 2018-08-06 16:17:11 +02:00
Gopkg.lock add a new main to generate random bugs 2018-08-16 18:22:00 +02:00
Gopkg.toml vendor gocui on the master branch because of no release in a while 2018-07-30 18:22:52 +02:00
LICENSE Create LICENSE 2018-07-12 12:54:04 +02:00
Makefile invert the behavior of the build flag for the webui 2018-09-02 00:06:50 +02:00
README.md Readme: recomend go get -u 2018-09-06 14:28:30 +02:00

git-bug

Distributed bug tracker embedded in Git.

Build Status License: GPL v3 GoDoc Go Report Card Gitter chat

Would it be nice to not have to rely on a web service somewhere to deal with bugs ?

Would it be nice to be able to browse and edit bug reports offline?

git-bug is a distributed bug tracker embedded in git. It uses git's internal storage so no files are added in your project.

As you would do with commits and branches, you can push your bugs to the same git remote you are already using to collaborate with other people.

🚧 This is for now a proof of concept. Expect dragons and unfinished business. 🚧

Install

Go get

go get -u github.com/MichaelMure/git-bug

If it's not done already, add golang binary directory in your PATH:

export PATH=$PATH:$GOROOT/bin:$GOPATH/bin

Pre-compiled binaries

  1. Go to the release page and download the appropriate binary for your system.
  2. Copy the binary anywhere in your PATH
  3. Rename the binary to git-bug (or git-bug.exe on windows)

That's all !

Linux packages

CLI usage

Create a new bug:

git bug new

Your favorite editor will open to write a title and a message.

You can push your new entry to a remote:

git bug push [<remote>]

And pull for updates:

git bug pull [<remote>]

List existing bugs:

git bug ls

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 <command> --help or read the command's documentation.

Interactive terminal UI

An interactive terminal UI is available using the command git bug termui to browse and edit bugs.

Web UI (status: WIP)

You can launch a rich Web UI with git bug webui.

Web UI screenshot 1 Web UI screenshot 2

This web UI is entirely packed inside the same go binary and serve static content through a localhost http server.

The web UI interact with the backend through a GraphQL API. The schema is available here.

Internals

Interested by how it works ? Have a look at the data model.

Misc

Planned features

  • media embedding
  • import/export of github issue
  • extendable data model to support arbitrary bug tracker
  • inflatable raptor

Contribute

PRs accepted. Drop by the Gitter lobby for a chat.

License

Unless otherwise stated, this project is released under the GPLv3 or later license © Michael Muré.

The git-bug logo by Viktor Teplov is released under the Creative Commons Attribution 4.0 International (CC BY 4.0) license © Viktor Teplov.