chore: ignore ruff-format reformat commits in git blame

[mateo-berri]

Relevant issues

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

There are no tests because this only adds two commit hashes to .git-blame-ignore-revs; there is no runtime behavior to assert on

Screenshots / Proof of Fix

This is a metadata-only change to .git-blame-ignore-revs, so there is no proxy behavior to curl. The effect is that git blame (and the GitHub Blame UI) skip the two mechanical reformat commits and point at the real authors of each line. Locally:

git config blame.ignoreRevsFile .git-blame-ignore-revs
git blame <file>   # lines no longer attributed to the reformat commits

Type

🧹 Refactoring

🚄 Infrastructure

Changes

Both #31317 (black to ruff format) and #31518 (unify ruff format width on 120) were pure mechanical reformats, each verified semantically inert by an AST-equivalence proof on its PR. Lines they touched currently show up under the reformat commit in git blame, which buries the real authorship. Adding the two reformat commit hashes to .git-blame-ignore-revs makes blame skip them, which is exactly what the existing entries in that file (the pydantic warning fix and the prettier dashboard run) already do

The hashes added are 430b5b8 for #31317 and 3dfbeab for #31518

---

Generated by Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[greptile-apps]

Greptile Summary

Adds two mechanical reformat commit hashes (430b5b8f for the ruff format migration and 3dfbeabe for the 120-char width unification) to .git-blame-ignore-revs so that git blame and the GitHub Blame UI skip those commits and surface the real author of each line.

• The pattern follows the existing entries in the file (pydantic warning fix, prettier dashboard run), using the same comment + hash format.
• No runtime code is touched; this is a pure developer-tooling metadata change with no effect on LiteLLM proxy behaviour.

Confidence Score: 5/5

Safe to merge — only adds two commit hashes to a developer metadata file with no effect on any runtime behaviour.

The change is two lines of metadata appended to .git-blame-ignore-revs following the exact same pattern already used by the existing entries in the file. No production code, tests, configuration, or schema is touched.

No files require special attention.

Important Files Changed

Filename	Overview
.git-blame-ignore-revs	Adds two ruff-format reformat commit hashes so git blame skips them and shows original authorship

_{Reviews (1): Last reviewed commit: "chore: ignore ruff-format reformat commi..." | Re-trigger Greptile}