unread library effect
(justintrouble.substack.com/p/extremism-and-the-unread-library)
justintrouble.substack.com/p/extremism-and-the-unread-library
(justintrouble.substack.com/p/extremism-and-the-unread-library)
justintrouble.substack.com/p/extremism-and-the-unread-library
This is one of my methods to begin thinking.
After spending months without any real self-awareness, this is an easy way to start being aware again.
Load a backpack with a tent and some drinks of choice. Find a potential camping spot where you can drop off the backpack, then walk more. No time limit, no destination. Ideally with drinks in hand, I like it as a partial distraction, but YMMV.
The tent need not be used. I just find it frees my mind to have, so I can stay in the woods for however long I feel like and nobody's expecting me back.
Problem: To release a new version of some software, I had to bash out at least four Magit commands in sequence:
The pain point is between 3 and 4, because it's a network connection you have to wait for, as much as 1000ms round-trip. Now just imagine doing this repeatedly over a few minutes because of a series of hot-fixes.
OK, so let's streamline this. Looking on the web, I discover the gitconfig option push.followTags
, which would merge steps 3 and 4. However, it only applies to something called "annotated tags".
So I initially discard that solution and move on… but wait. OK, annotated tags sound like a PITA, but actually they can be automated, by Magit especially.
So let's use them. Add to ~/.gitconfig
:
[push] followTags = true
Then, stop typing t t
in Magit to tag, and instead type out t - a r
.
(This creates an annotated release tag. and "release tag" is just a Magit convenience to pre-populate the prompt.)
Next time you push, the tag is sent along.
(Sorted by recent first)