Ethan Estrada eestrada

Since version 2.23, git-blame has a feature to ignore certain commits. This feature is useful to ignore large formatting or apparently unimportant changes.

How to use

Create a revisions list file. The file name is usually .git-blame-ignore-revs
Set the file as a default ignore file for blame by git config blame.ignoreRevsFile .git-blame-ignore-revs

The file format is described in git-fsck's man: https://git-scm.com/docs/git-fsck#Documentation/git-fsck.txt-fsckskipList

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

	#!/bin/bash

	if test -z "$1"; then
	echo "Usage: $0 <prompt>"
	exit 1
	fi

	if test -z "$OPENAI_API_KEY"; then
	echo "OpenAI key is missing - \$OPENAI_API_KEY must be set"
	exit 1

	defaults write com.apple.Dock appswitcher-all-displays -bool true
	killall Dock