aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Muré <batolettre@gmail.com>2020-03-01 14:36:59 +0100
committerMichael Muré <batolettre@gmail.com>2020-03-01 14:45:39 +0100
commitf82ad38671ab42690d83675166e5eefa03d74d85 (patch)
tree41c6c2ed17a1fa6e41726f6a135c7dd710e896f6
parente53d7c6561fd4f0f7f96f67ea14c64f1333bd6cc (diff)
downloadgit-bug-f82ad38671ab42690d83675166e5eefa03d74d85.tar.gz
howto: link to other ressources
-rw-r--r--doc/howto-github.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/howto-github.md b/doc/howto-github.md
index 672aa8b2..a441d15d 100644
--- a/doc/howto-github.md
+++ b/doc/howto-github.md
@@ -18,6 +18,8 @@ This has several upsides:
- you get to choose the UI you prefer between CLI, interactive terminal UI or web UI
- you get a near complete backup in case Github is down or no longer fit your needs
+Note: at the moment, Gitlab and Jira are also fully supported.
+
## Installation
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`.
@@ -67,3 +69,12 @@ The command line tools are really meant for programmatic usage or to integrate `
For a richer and more user friendly UI, `git-bug` proposes a web UI (read-only at the moment). You can start it with `git bug webui`:
![web UI screenshot](../misc/webui2.png)
+
+## Want more?
+
+If you interested to read more about `git-bug`, have a look at the followings:
+- [the project itself, with a more complete readme](https://github.com/MichaelMure/git-bug)
+- [a bird view of the internals](https://github.com/MichaelMure/git-bug/blob/master/doc/architecture.md)
+- [a description of the data model](https://github.com/MichaelMure/git-bug/blob/master/doc/model.md)
+
+Of course, if you want to contribute the door is way open :-) \ No newline at end of file