From 733107eacf137240e9cd90118fcc87c5c7906015 Mon Sep 17 00:00:00 2001
From: Karl von Randow <karl@xk72.com>
Date: Sun, 19 Jan 2025 09:49:26 +1300
Subject: [PATCH] chore: .git-blame-ignore-revs

---
 .git-blame-ignore-revs |  3 +++
 README.md              | 10 ++++++++++
 2 files changed, 13 insertions(+)
 create mode 100644 .git-blame-ignore-revs

diff --git a/.git-blame-ignore-revs b/.git-blame-ignore-revs
new file mode 100644
index 0000000..ad405d5
--- /dev/null
+++ b/.git-blame-ignore-revs
@@ -0,0 +1,3 @@
+0132a03f217ca837561e56135bd8d59cc36c8fe5
+ca9fc91497bf184dff936de227ce95cd94ec57aa
+0bd7ab3c2656fbdaf7130276cb57e2156ac8b3bc
diff --git a/README.md b/README.md
index e3e2aa8..907828b 100755
--- a/README.md
+++ b/README.md
@@ -230,6 +230,16 @@ That will prompt you to indicate whether your change is a patch (a bug fix) or a
 
 Changesets will create a new file in the `.changeset` directory that you can commit as part of your PR.
 
+### `.git-blame-ignore-revs`
+
+Some revisions in the git history are spurious in a git blame, such as linting the code base.
+These revisions are listed in `.git-blame-ignore-revs`. You can configure your local git repository
+to use this file to skip these revisions in a blame:
+
+```shell
+git config blame.ignoreRevsFile .git-blame-ignore-revs
+```
+
 ### `config.schema.json`
 
 Useful references for the `config.schema.json`: