All posts

Find Who Changed What and When in Git

Git already stores every change, every commit, and every author. But finding the exact person, the file they changed, and the precise time they did it can be painful if you don’t know where to look. The good news: Git makes this possible in seconds, once you know the right commands. Find Who Changed a Line in Git When you need a surgical answer, git blame is the go-to. It shows the commit hash, author name, and timestamp for each line in a file. git blame path/to/file You can zoom in on a

Free White Paper

Just-in-Time Access + Git Commit Signing (GPG, SSH): The Complete Guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free. No spam. Unsubscribe anytime.

Git already stores every change, every commit, and every author. But finding the exact person, the file they changed, and the precise time they did it can be painful if you don’t know where to look.

The good news: Git makes this possible in seconds, once you know the right commands.

Find Who Changed a Line in Git

When you need a surgical answer, git blame is the go-to. It shows the commit hash, author name, and timestamp for each line in a file.

git blame path/to/file

You can zoom in on a specific range to speed up the search:

git blame -L 45,60 path/to/file

Now you know exactly who last touched those lines, and when.

Track File History

Sometimes the problem isn’t a line; it’s the whole file. Use git log with path filtering:

git log -- path/to/file

Add -p to see the actual changes:

Continue reading? Get the full guide.

Just-in-Time Access + Git Commit Signing (GPG, SSH): Architecture Patterns & Best Practices

Free. No spam. Unsubscribe anytime.
git log -p -- path/to/file

You now have the entire history of that file, from the first commit to the last edit.

See Who Accessed What and When Across the Repository

When something big breaks, pinpointing a suspect commit across the repo can be faster than checking one file at a time.

git log --stat

This shows each commit, what files it changed, and how many lines were added or removed. Pair it with --author to filter by person:

git log --author="Name"

Or use --since and --until to hunt changes in a time window:

git log --since="2024-01-01"--until="2024-02-01"

Detect Access Patterns, Not Just Changes

Git only logs changes, not reads. If you want a real audit log of file access, code viewing, and clone operations, you need monitoring at the hosting or infrastructure layer. On self-hosted setups, configure server-side hooks or enable logging at the Git server. On managed services, check activity logs in your Git host dashboard.

Why This Matters

Knowing who accessed what and when is not about finger-pointing. It’s about speed. The faster you can trace the source, the faster you can fix bugs, secure your repo, and keep your release cycle intact.

And you don’t have to wire it all by hand. You can connect your repository to tools that give you instant visibility — commit history, file access, and user actions — without custom scripts.

Hoop.dev makes it possible to set this up in minutes. You’ll watch commits, file-level edits, and activity roll in live, right in your browser. No guessing. No trawling logs. Just answers. See it in action today, and get complete visibility the moment you need it most.

Get started

See hoop.dev in action

One gateway for every database, container, and AI agent. Deploy in minutes.

Get a demoMore posts