blob: 40b2e22d2535503a7dccf1d64dad27f251cf447d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
# git-bug
[![Build Status](https://travis-ci.org/MichaelMure/git-bug.svg?branch=master)](https://travis-ci.org/MichaelMure/git-bug)
[![License: GPL v3](https://img.shields.io/badge/License-GPLv3+-blue.svg)](http://www.gnu.org/licenses/gpl-3.0)
[![GoDoc](https://godoc.org/github.com/MichaelMure/git-bug?status.svg)](https://godoc.org/github.com/MichaelMure/git-bug)
[![Go Report Card](https://goreportcard.com/badge/github.com/MichaelMure/git-bug)](https://goreportcard.com/report/github.com/MichaelMure/git-bug)
> Distributed bug tracker embedded in Git
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 report offline ?
`git-bug` is a distributed bug tracker embedded in `git`. It use 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 your are already using to collaborate with other peoples.
:construction: This is for now a proof of concept. Expect dragons and unfinished business. :construction:
## Install
### Go get
```shell
go get github.com/MichaelMure/git-bug
```
If it's not done already, add golang binary directory in your PATH:
```bash
export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
```
### Pre-compiled binaries
1. Go to the [release page](https://github.com/MichaelMure/git-bug/releases/latest) 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 !
## 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](doc/md/git-bug.md).
## Interactive terminal UI
An interactive terminal UI is available using the command `git bug termui` to browse and edit bugs.
<p align="center">
<img src="https://cdn.rawgit.com/MichaelMure/git-bug/55ab9631/doc/termui_recording.svg">
</p>
## Web UI (status: WIP)
You can launch a rich Web UI with `git bug webui`.
![Web UI screenshot 1](doc/webui1.png)
![Web UI screenshot 2](doc/webui2.png)
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](graphql/schema.graphql).
## Internals
Interested by how it works ? Have a look at the [data model](doc/model.md).
## Misc
- [Bash completion](misc/bash_completion)
- [Zsh completion](misc/zsh_completion)
- [ManPages](doc/man)
## Planned features
- media embedding
- import/export of github issue
- extendable data model to support arbitrary bug tracker
- inflatable raptor
## Contribute
PRs accepted.
## License
GPLv3 or later © Michael Muré
|