[cruessler]

This PR adds a benchmark for gix-blame. This will hopefully be the basis for some upcoming work on gix-blame that I intend to do.

The benchmark is deliberately simple, and it deliberately does not set up a synthetic repository, but measures gix_blame::file() on a set of files from the gitoxide repository itself. I hope that the files I chose are somewhat representative of real-world workloads.

The benchmark only measures gix_blame::file(), excluding the time it takes to construct and destruct the resource cache.

# to capture a baseline
cargo bench -p gix-blame --bench blame -- --save-baseline baseline

# to compare a change against a captured baseline
cargo bench -p gix-blame --bench blame -- --baseline baseline

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-25T17:19:43.912308Z	950f408	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "Codex (@codex) review" or "Codex (@codex) security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Byron]

Thanks!

In future, I'd hope to see what's in the PR description in the commit as well, as I still think that having as much context as possible in the commit history is valuable, also in the long run. Also no need to rely on information that is on GitHub exclusively.