From ecc0a4311ab99582cf4a37a06273c0b4b9fb3256 Mon Sep 17 00:00:00 2001 From: MotherSphere Date: Sat, 25 Jul 2026 13:41:47 +0200 Subject: [PATCH] chore: ignore pure-move commits in git blame The module split moved ~2000 lines, so blame pointed at that commit for a large part of src/. Recording it here sends blame back to the change that actually wrote each line. Future move-only commits go in the same list. --- .git-blame-ignore-revs | 9 +++++++++ 1 file changed, 9 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..5287df4 --- /dev/null +++ b/.git-blame-ignore-revs @@ -0,0 +1,9 @@ +# Commits that only MOVE code and never change behaviour. Listing them here keeps +# `git blame` pointing at the change that actually wrote each line instead of at +# the move. GitHub honours this file automatically; locally, enable it once with: +# +# git config blame.ignoreRevsFile .git-blame-ignore-revs + +# refactor: split the four most-edited modules into directories +# (update/ + app.rs + i18n/ + github/, ~2000 lines moved, no behaviour change) +430f23840a63e3e69843215d27f87365057e4e34