How to see who edited what in GitHub?

 
Step 1: Navigate to the repository on GitHub
 

Visit your project’s main page in a web browser. Make sure you are signed in and have read access.

• Open https://github.com in your browser.
• Click your profile avatar and select Your repositories.
• Choose the repository you want to inspect.

 
Step 2: View the repository’s commit history
 

The commit history shows who made changes and when.

• On the repository page, click the Commits link above the file list.
• You’ll see a chronological list of commits, each showing the author’s avatar, name, date, and commit message.

 
Step 3: Inspect a specific commit
 

Click any commit entry to see all file changes in that commit.

• Click the commit message or hash.
• Review the diff view: additions are highlighted in green, deletions in red.
• The top of the page shows the author and committer details.

 
Step 4: Use the Blame view on GitHub’s web interface
 

The Blame view attributes each line in a file to the commit and author that last modified it.

• Navigate to the file you want to inspect.
• Click the Blame button (it looks like a clock icon).
• Scroll through the file. Each line is annotated with: author avatar, commit hash, and date.

 
Step 5: Run Git commands locally for detailed history
 

If you prefer your terminal, clone the repo and use git log and git blame.

git clone https://github.com/username/repo.git
cd repo

Use Git log to see commit history:

git log --oneline --decorate

Filter by author:

git log --author="Alice" --stat

Use Git blame on a file:

git blame path/to/file.ext

 
Step 6: Explore contributor insights
 

GitHub provides visual charts and contributor lists in the Insights tab.

• On your repository page, click Insights in the top menu.
• Select Contributors to see a graph of code frequency by each contributor.
• Hover over bars to view commit counts and contributions over time.

 
Step 7: Search commits and authors with advanced filters
 

GitHub’s search can narrow down commits by author, file, or message.

• Use the search box in the repository and select Commits from the dropdown.
• Enter queries like: author:Alice path:src/app.js
• Combine filters, for example: author:Bob merged:true fix

 
Step 8: Summarize findings and export data (optional)
 

You can export commit data or copy blame annotations for reporting.

• On any commit page click the Download patch link to save the diff.
• Copy blame lines directly from the web interface or redirect git blame output to a file:

git blame path/to/file.ext > blame-report.txt