Search

Super useful walkthrough on taking a branch from one repository and publishing it to another repository entirely (great for creating test repos or stripped-down example repos for bug …

A short guide to removing Git history entirely. Particularly useful when you're forking an existing project as a base for something …

A self-hosted, open-source IndieAuth authorisation endpoint. I still find myself running in circles as to whether IndieAuth worries me or excites me, but I find this project a …

Whilst falling down the rabbit-hole of digital gardening I found some of Maggie's tweets incredibly insightful and useful, yet somehow totally missed her own digital garden (and her entire related …

The debate around the common practice of naming the primary branch in Git "master" continues, but I thought the statement from WordPress had some interesting points. They largely mirror my own views …

I was recently given a new laptop at work (🥳), but failed to realise that my Git author details weren't syncing correctly with GitHub for almost a month... 🤦 Rather than simply accept those white squares, I decided to rewrite the repository history. The process turns out to be quite simple, but I still hit several snags so figured it could be useful to document my fixes and errors.

Notes from the fully remote React Summit 2020 (or at least the talks I tuned in for). Lots covered, from static-site generators and the Jamstack through to React state management and accessibility. What a fun day!

There has been a lot of web chatter around the launch of Deno, the new JavaScript runtime engine. Their introductory blog post does a great job of explaining when you should use it (and conversely …

Turns out it's pretty simple to rename any branch in Git. Scott has a full step-by-step guide, but there are a few …

There are several strong arguments for moving away from using "master branch" as default terminology, but what should it be replace with? Personally, I like the idea of extending the tree abstraction that we use when talking about branches, so have started using "trunk".

The combination of the Carbon design system and NextJS should make for rapid website development, but I ran into a few small hurdles getting them to play nicely with one another using existing documentation and community guidelines.

A look at how I've been using Git aliases to remove repetitive tasks, automate workflows, and generally optimise working on the command line. They're small tips, but they've had a big impact on me.

I've been saying for years that React feels like jQuery did circa 2010: it's used everywhere, its devotees are numerous, but the leading edge left it in the dust a while ago. I do think that Hooks …

Need to self-host your front end away from the "modern" services like Netlify or Vercel? As both continue to get a little sketchier with time, it's definitely something I'm having to …

Mastodon makes saving interesting links for later very easy, but getting these into a feed reader or note-taking service seemed impossible until I came across a neat little hosted solution.

How to change your Git author details for a single codebase, and check that the changes have taken effect.

Or how I spent four days trying to debug a local Astro environment that refused to load any CSS.