MichaelMure/git-bug
1
1
Fork 0
mirror of https://github.com/MichaelMure/git-bug.git synced 2024-12-13 20:13:15 +03:00
Code Issues Projects Releases Wiki Activity

doc: refresh the github howto

Browse Source
This commit is contained in:
Michael Muré 2020-03-01 12:50:22 +01:00
parent 710d85664e
commit 8365c6334e
No known key found for this signature in database
GPG Key ID: A4457C029293126F
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -28,7 +28,7 @@
:construction: This is now more than a proof of concept, but still not fully stable. Expect dragons and unfinished business. :construction:
## Install
## Installation
<details><summary>Pre-compiled binaries</summary>

12
doc/howto-github.md
View File

@ -2,8 +2,16 @@
[git-bug](https://github.com/MichaelMure/git-bug) is a standalone distributed bug-tracker that is embedded in git. In short, if you have a git repository you can use it to store bugs alongside your code (without mixing them though!), push and pull them to/from a normal git remote to collaborate.
<p align="center">
<img src="../misc/diagrams/native_workflow.png" alt="Native workflow">
</p>
Bridges with other bug-trackers are first-class citizen in `git-bug`. Notably, they are bidirectional, incremental and relatively fast. This means that a perfectly valid way to use `git-bug` is as a sort of remote for Github where you synchronize all the issues of a repository to later read and edit them and then propagate your changes back to Github.
<p align="center">
<img src="../misc/diagrams/bridge_workflow.png" alt="Bridge workflow">
</p>
This has several upsides:
- works offline, including edition
- browsing is pretty much instant
@ -12,7 +20,7 @@ This has several upsides:
## Installation
Follow the [installation instruction](https://github.com/MichaelMure/git-bug#install). The simplest way is to download a pre-compiled binary from [the latest release](https://github.com/MichaelMure/git-bug/releases/latest) and to put it anywhere in your `$PATH`.
Follow the [installation instruction](https://github.com/MichaelMure/git-bug#installation). The simplest way is to download a pre-compiled binary from [the latest release](https://github.com/MichaelMure/git-bug/releases/latest) and to put it anywhere in your `$PATH`.
Check that `git-bug` is properly installed by running `git bug version`. If everything is alright, the version of the binary will be displayed.
@ -22,9 +30,9 @@ Check that `git-bug` is properly installed by running `git bug version`. If ever
1. Choose `github`.
1. Type a name for the bridge configuration. As you can configure multiple bridges, this name will allow you to choose when there is an ambiguity.
1. Setup the remote Github project. The wizard is smart enough to inspect the git remote and detect the potential project. Otherwise, enter the project URL like this: `https://github.com/MichaelMure/git-bug`
1. Enter your login on Github
1. Setup an authentication token. You can either use the interactive token creation, enter your own token or select an existing token, if any.
1. Run `git bug bridge pull` and let it run to import the issues and identities.
1. Find your imported identity by running `git bug user ls` and select it as your own with `git bug user adopt <id>`
## Basic usage