···

       
1
       
1
       
+
       
---

     

       
2
       
2
       
+
       
date: 2021-02-21T14:41:04.750-08:00

     

       
3
       
3
       
+
       
category:

     

       
4
       
4
       
+
       
  - git-bug

     

       
5
       
5
       
+
       
  - moaparty

     

       
6
       
6
       
+
       
  - git

     

       
7
       
7
       
+
       
  - GitLab

     

       
8
       
8
       
+
       
---

     

       
9
       
9
       
+
       
I get excited when I have a chance to try new software and...it just works! That was the case with [[git-bug]]. It's a bug tracker that is fully embedded in git. You use the same git repo that you are using for code development to track and update bugs and issues.

     

       
10
       
10
       
+
       


     

       
11
       
11
       
+
       
On [[MacOS]], `brew install git-bug` and you're up and running. 

     

       
12
       
12
       
+
       


     

       
13
       
13
       
+
       
`git bug user create` will setup your local user. It will read from your local git settings for full name and email address. The only other thing you'll need is a full link to an avatar image -- the picture that represents you.

     

       
14
       
14
       
+
       


     

       
15
       
15
       
+
       
Next up is setting up bridges. git-bug supports [[GitLab]], [[GitHub]], [[JIRA]], and minor support for [[Launchpad]], as well as custom implementations.

     

       
16
       
16
       
+
       


     

       
17
       
17
       
+
       
The [[Moa Party]] project is what I'm going to experiment using git-bug on, which we host on [[GitLab]]. You run `git bug bridge configure` and walk through a terminal interface to fill out your GitLab server details (yes, you can use it with self-hosted GitLab instances), as well as your personal login and an access token.

     

       
18
       
18
       
+
       


     

       
19
       
19
       
+
       
When you create a personal access token, you'll need to give it api access permission, which pretty much can do everything on your behalf. I initially created a token without that access, and had a heck of a time figuring out how to fix that. Turns out, go into your local `~/.gitconfig` and delete the token and identity with the wrong permissions. And, `git-bug bridge rm` the original bridge you created with the wrong token, then you can `git-bug bridge configure` a new default.

     

       
20
       
20
       
+
       


     

       
21
       
21
       
+
       
And now, unfortunately, I nuked identities using the Makefile (and found [@agentofuser in the issues from a couple of years ago](https://github.com/MichaelMure/git-bug/issues/230)) and am currently in a state where I can't create a new identity.

     

       
22
       
22
       
+
       


     

       
23
       
23
       
+
       
Since the [[Agora]] itself works with git a lot, we may actually be able to link git-bugs with the Agora itself in some way, but that's pretty deep git magic for me, since I don't fully understand how git-bug works / where it stores stuff in git.