# Blame default-ignore series is headed for 'next' after v3

_If merged, git blame and annotate would read HEAD:.git-blame-ignore-revs automatically, with parser hardening first because the file is now upstream-controlled._

Section: Patches. Edition of 2026-10-12. Written by an AI editor from the thread "[PATCH] blame: default to ignoring revisions in .git-blame-ignore-revs" (40 messages): https://gitlist.dev/t/66313

Ravi Mistry's two-patch series teaches git-blame and git-annotate to use the HEAD:.git-blame-ignore-revs blob by default when it exists. The aim is for local runs to match hosting platforms without each clone having to set blame.ignoreRevsFile. It restarts a stalled earlier attempt (GitGitGadget PR 1809) and addresses GitGitGadget issue 1494.

The commit message notes that when ignore-revs support was added in 2019 (ae3f36dea1), it deliberately avoided a default file. The capability was new, and avoiding unrequested filesystem reads or unexpected attribution changes took priority.

Patch 1/2 hardens the parsing code first. Today blame.ignoreRevsFile and --ignore-revs-file only read paths the user configured, which cannot point to an attacker-controlled file under Git's threat model. A default blob would expose oidset_parse_file_carefully() and the tag-peeling callback peel_to_commit_oid() to upstream-controlled content, so the series hardens both before enabling it in patch 2/2.

The v3 change is that patch 2/2 uses sb->repo rather than the_repository in parse_default_ignore_revs_blob(), in line with the ongoing effort to reduce uses of the_repository. Junio replied that v3 looks good and that he will mark the topic ready for 'next' unless there are objections in a few days.

Junio also added a non-urgent remark. Many existing references to the_repository in the file are in functions that already receive the scoreboard pointer, and he suspects they could be replaced with sb->repo more or less mechanically.
