Skip to main content
The git log command displays your project’s commit history directly in the terminal. It provides essential details for each commit, including the commit hash, author name, commit date, and commit message. Understanding these components is critical for tracking changes, debugging issues, and collaborating effectively.
Using git log can help you quickly identify important commits in your project history, making it easier to revert to previous states or understand code evolution.

​
Default Git Log Output

When you run the git log command without any options, it presents detailed information for each commit. Below is an example of the default output: 
$ git log
commit 67c833e3…ecb7df62f (HEAD -> master)
Author: John Doe <john@doe>
Date:   Sun Jun 14 14:45:07 2020 -0700

    Added first story
In this output:
  • Commit Hash: A unique identifier for the commit.
  • Author: Name and email of the person who made the commit.
  • Date: When the commit was created.
  • Message: A brief description of the changes made.

​
One-line Commit View

If you prefer a more concise overview of your commit history, the --oneline option condenses each commit into a single line. This format is perfect for a quick scan through the project’s history: 
$ git log --oneline
67c833e (HEAD -> master) Added first story
This compact format emphasizes the commit hash and the commit message, making it easier to browse through many commits quickly.

​
Customizing Git Log Output

Git log offers various configuration options to tailor the display of commit history to your needs. You can combine different options to achieve custom formats, filter commits, and graphically represent branch structures. Experimenting with these options can provide deeper insights into your project’s development flow. For additional details, refer to the Git Documentation. By mastering these git log options, you will enhance your version control workflow and gain a better understanding of your project’s evolution.

Watch Video

Practice Lab