Log tweaks and git-bug note

_logs/20210221-2241.md

@@ -1,12 +1,13 @@
----
-date: 2021-02-21T14:41:04.750-08:00
-category:
-  - git-bug
-  - moaparty
-  - git
-  - GitLab
----
-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.
+---
+date: 2021-02-21T14:41:04.750-08:00
+tags:
+  - git-bug
+  - moaparty
+  - git
+  - GitLab
+---
+
+I get excited when I have a chance to try new software and...it just works![^1] 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.
 
 On [[MacOS]], `brew install git-bug` and you're up and running. 
 
@@ -20,4 +21,14 @@ When you create a personal access token, you'll need to give it api access permi
 
 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.
 
-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.
+---
+
+OK, I got it working through the age old trick of ... downloading a new copy of the repo and setting it up again. 
+
+There is a recent (7 days ago) [issue thread](https://github.com/MichaelMure/git-bug/issues/366) that seems to indicate the GitLab API has been improved and this can be working again. git-bug itself works, and I managed to import the existing GitLab issues, but I can't push changes to the GitLab issues.
+
+---
+
+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.
+
+[^1]: Of course, further down in this note, after a bunch of git surgery, things did not just work! But you can see the screenshots of things working in the [[git-bug]] page.

_notes/git-bug.md

@@ -0,0 +1,14 @@
+---
+title: git-bug
+git: https://github.com/MichaelMure/git-bug
+---
+
+Distributed, offline-first bug tracker embedded in git, with bridges to [[GitHub]], [[GitLab]], and [[JIRA]], for two way syncing of issues.
+
+Screenshot of the terminal UI:
+
+![]({% link assets/2021/02/git-bug-termui.png %})
+
+Screenshot of the (local) web UI:
+
+![]({% link assets/2021/02/git-bug-webui.png %})

log.html

@@ -1,5 +1,5 @@
 ---
-title: Log
+title: Logs
 layout: feed
 content-type: eg
 permalink: /logs/
@@ -9,8 +9,10 @@
 {%- for item in sortednotes limit: 20 -%}
 
   <article>
-  {{ item.content | markdownify }}
-  <div><a href="{{ item.url }}">#</a></div>
+  <div><a href="{{ item.url }}">
+  {% assign d = item.date | date: "%-d" %}{{ item.date | date: "%B" }} {% case d %}{% when "1" or "21" or "31" %}{{ d }}st{% when "2" or "22" %}{{ d }}nd{% when "3" or "23" %}{{ d }}rd{% else %}{{ d }}th{% endcase %}, {{ item.date | date: "%l:%M%P" }}
+  </a></div>
+  <p style="margin-left: 30px">{{ item.content | remove: "<p>" | replace: "</p>", "<br /><br />" | truncate: 500 }}</p>
   </article>
 
 {%- endfor -%}