author-contributions

To trace git contributions across branches with renames, you need to locate the author's identity, gather touched files, and build a rename map. This process classifies changes as DIRECT or VIA_RENAME to preserve authorship history during audits.

Yes, you can audit files a specific user modified on a branch compared to upstream before a merge. The process identifies the author's exact identity, gathers all touched files, and summarizes results with a diff-like table for code reviews.

Finding all files touched by an author on a git branch involves locating their exact identity and gathering touched files. It builds a rename map to classify contributions as DIRECT or VIA_RENAME, producing a concise diff-like table for reconciliation.

Git does not automatically preserve authorship history for renamed files during branch reconciliation. You must explicitly build a rename map across commits to classify contributions as DIRECT or VIA_RENAME and trace the author's changes.

The best way to review code changes by a specific author when file paths change is to build a rename map across commits. This classifies contributions as DIRECT or VIA_RENAME, providing a concise table suitable for code reviews and audits.

An upstream branch audit misses contributions from renamed files because standard diffing does not trace path changes. Building a rename map across commits is required to classify these contributions as VIA_RENAME and preserve authorship history.