search

qmacro / thinking-aloud

A journal, of sorts.
13 stars 0 forks source link

2021-03-25 12:09:25 What else do I need for the basic setup of my jour… #9

Open qmacro opened 3 years ago

qmacro commented 3 years ago

What else do I need for the basic setup of my journalling here with Thinking Aloud?

On the one hand, I don't want to over-complicate things - part of the idea is to have a minimal setup. On the other hand, there are probably aspects that I'm still missing.

One in particular is the ability to "go meta". In other words, I want to be able to raise issues for the repo-based journalling mechanism itself, so I can record something that's amiss and then get around to addressing that.

But while I'm using issues in the simplest possible way, that's not going to work, as I'll pick up those "real" issues too in my journalling output. So it's time to turn to labels. I've alluded to the use of labels, which can be assigned to issues on GitHub, and while I was thinking more about journal entry categories, I really need a label to distinguish actual journal entries from non-journal entries.

I was originally thinking of having a label for non-journal entries, such as "issue", but that seems a little silly; better to have a positive "entry" label, as I can easily add that to my "new journal entry" mechanism - the gh GitHub CLI lets me assign labels on issue creation, like this:

; gh issue create --label entry --title "..."

Then it's easy to show the list of actual journal entry issues, using the very capable search & filter syntax. I think this is what I'll implement next, and then I can record this sort of "missing feature" entry as an actual issue rather than an entry.

qmacro commented 3 years ago

So I think I've done this now, I've added the --label entry to the new entry flow, and also modified the workflows to ensure the jobs only ran on entry style issues, in #10. Since this change, I also streamlined the jobs, in #12.