I'm still itching to try jujutsu in more details, but every time I dive in the documentation, I feel like I'm missing a piece. I've been wondering if I just need to "see it at work", see how someone actually uses it, especially from my perspective. This post is much closer to that and I found it useful.

A good git workflow for small teams. Reading it, it happens to be the one we use in my team, and I can confirm it's a very effective one!

An interesting library to record ML experiments metadata through commit messages. Even better, it supports a query language to find which commit satisfies a given criterion.

I've been more and more tempted by jujutsu as a drop-in replacement for git. Its default way to handle changes seems so sane compared to git. This article is a very thorough and accessible introduction to how it works, and it definitely nudged me further along the jj train.

Useful example of a git worktree workflow. Worktrees help avoiding all the stashing and branch hopping a typical workflow would have. You can pull the repository multiple times on different branches and work on different features, review pull requests, run automated tests, etc..., without having to break your flow.

I always have to google Github actions format and snippets, or prompt an LLM for it. This is a collection of examples so you never have to google it again.