Luke Moderwell lukemoderwell

Hotfixing is pretty simple but moving commits between different branches can get a little hairy if you're not careful. The trouble we often experience usually results from not paying attention to which branch you're on when you create the commits.

The following steps outline a recommended approach which should reduce any confusion or potential for regression.

Fetch all upstream updates from the remote (e.g. Github)

$ git fetch --all 
$ git pull --all

Build a Second Brain for Your Business with Claude Code

A 7-step quick start for solopreneurs, consultants, and small teams.

What This Is

This guide walks you through building a "second brain" — a local knowledge base that Claude Code can read, write, and reason over. Think of it as giving Claude persistent memory about your business: clients, projects, SOPs, decisions, and commitments. You talk to it like a colleague who already knows the context.

Build a Second Brain for Your Business with Claude Code

A 7-step quick start for solopreneurs, consultants, and small teams.

What This Is

This guide walks you through building a "second brain" — a local knowledge base that Claude Code can read, write, and reason over. Think of it as giving Claude persistent memory about your business: clients, projects, SOPs, decisions, and commitments. You talk to it like a colleague who already knows the context.

	#!/usr/bin/env bash
	autopick() {
	git fetch --all &&
	git checkout release &&
	git pull &&
	git submodule update &&
	git checkout -b hotfix/rel-$2 &&
	git cherry-pick $1 &&
	git push -u origin hotfix/rel-$2 &&
	git checkout master &&