#git

Run git log --graph on most team projects and you’ll see the problem. Parallel lines everywhere, merge commits that just say “Merge branch ‘feature/x’ into develop”. None of it useful. It’s noise. I’ve been using a rebase-based workflow for years to avoid this. The history stays linear and the diffs stay readable. This post covers both the argument and the specific branch structure I use for team feature work.

I have a “now playing” widget on my /now page that shows the last track scrobbled to Last.fm. It’s powered by a GitHub Actions workflow that polls the Last.fm API every hour and commits the result to the repo. It worked fine, but quietly polluted my commit history.

The amount of personal data that we give away these days is insane. It’s true of a huge number of online services that “free isn’t free”, and that your personal data is the virtual currency by which you’re able to use so many great services for “free”.

git is a powerful tool. After using it for the past couple of years I’m still finding new/powerful things that can be done with it.