How do I see git log commits by a specific author?

Use git log --author="Jane Doe" to filter commits by author. The pattern is a case-sensitive regex, so a partial name like git log --author="Jane" also works and is often enough to find your own commits.

How do I show git log in one line per commit?

Run git log --oneline . It condenses each commit to an abbreviated hash and its subject line, which is ideal for quickly scanning history. Combine it with --graph --decorate to also see branch structure and tag names.

How do I search git log commit messages for a keyword?

Use git log --grep="pattern" to filter commits whose messages match a regular expression, and add -i for a case-insensitive search. This is the fastest way to find commits referencing a feature name or an issue ID such as Fixes #123 .

How do I find which commit added or removed a specific line of code?

Use the pickaxe option git log -S"some_string" to find commits where the number of occurrences of that string changed. Follow up with git log -p -n 1 <hash> to inspect the exact diff of the commit responsible.

Since I usually work on several projects simultaneously, I often start my day with a Git log to see where I should continue my coding or writing. I think that Git log is one of the most important commands.

git log: Viewing Git Commit History

git log is a Git command that displays a repository’s commit history, listing each commit with its author, date, and message. It lists all commits with details such as the author’s name, commit date, and descriptive messages explaining what was changed or fixed. This makes it an essential tool for tracking feature launches, debugging issues, and efficiently collaborating within a team.

This post explores various useful options for a git log, enabling you to quickly gain insights into your project’s history. Let’s go!

How to Use git log

🔒 Subscribe to keep reading.

Top 10 Most Useful git log Options

🔒 Subscribe to keep reading.

Conclusion: Using git log to Navigate Project History

🔒 Subscribe to keep reading.

References

🔒 Subscribe to keep reading.

You've hit a Deep Dive tutorial.

I spend dozens of hours researching, coding, and breaking things to write these guides. This content is free, but reserved for my subscriber community. Drop your email below to unlock this guide (and all past/future deep dives):

Already a subscriber? Use the magic link from your last newsletter, or reset your password.

New subscribers get an inbox mail: Set a password to unlock articles. The form does not log you in — use the same email afterwards.

Git Log

📚 This post is part of the "Git Survival Guide" series

git log: Viewing Git Commit History

How to Use git log

Top 10 Most Useful git log Options

Conclusion: Using git log to Navigate Project History

References

References

Citation

Git Log

📚 This post is part of the "Git Survival Guide" series

git log: Viewing Git Commit History

How to Use git log

Top 10 Most Useful git log Options

Conclusion: Using git log to Navigate Project History

References

You're in

References

Citation