¿Plugin?: git-linearize and/or lucky_commit

[feefladder]

First off: I really like git-branchless, in how it enables your git tree to actually look like a tree:

              1
             /
a-b-c-d-e-f-0-1
           \     i
            \   /
             g-h
                \
                 i

in stead of not-a-tree:

a-b-c-d-e-f-g-h-i
   \     /      <- normally trees don't merge
    c-d-e 

especially, a git-branchless tree looks like a scotch pine:

In that branches at the bottom die off and then you'll end up with a thin, long trunk with few branches at the top. However, how do you signal to people that a specific commit is unlikely to be changed? (except for fast-forwarding the main branch).
Well, what I use is extremely-linear, so your shorthashes look like:

◆ 0000027028 17m (ᐅ main) Nice commit message
┃
◯ 1aec231 1m Work in progress

Now, because it takes some effort to use lucky-commit before changing, having a formatted shorthash is a "soft" way of saying: This commit is rather final.

Here comes the catch: After some sadness with rebasing, I've rewritten extremely-linear to use git-branchless. It works rather nicely, but some things are still missing:

• Using hide -D, the commit is hidden from git sl, but still show up in git log --graph --all.
• How to handle merge commits? Maybe implement some sort of BFS that prefers the shortest path and/or the main branch using git log --first-parent main <- bash isn't ideal for BFS, but it is nice for calling Git commands?

lucky_commit is written in Rust, just like git-branchless. So maybe this could become a plugin or extension to git-branchless? Well, anyways, this post is also meant to be semi-humorous, I hope that came across 😆