How to Get Commit History in Git?

Commit history in Git is a record of changes made to a repository over time. It provides insights into what was changed, who made the changes, and when they were made. Viewing commit history is essential for understanding project evolution, debugging issues, and tracking contributions.

In this blog, you’ll learn how to retrieve and interpret commit history using Git.

What Is Commit History in Git?

Commit history is a sequential log of all the commits made in a repository. Each commit contains:

• A unique hash identifier.
• Author information (name and email).
• Date and time of the commit.
• A commit message describing the changes.

---

How to View Commit History

1. Using the Command Line

a. Basic Commit History

To view a simple list of commits:

git log

This command displays:

• Commit hash.
• Author’s name and email.
• Date and time.
• Commit message.

b. Condensed Commit History

To get a one-line summary of each commit:

git log --oneline

Example output:

abcd123 Added new feature
efgh456 Fixed login bug
ijkl789 Initial commit

c. Graphical Commit History

For a visual representation of branches and commits:

git log --oneline --graph --all

This command shows the commit history in a graph-like structure, highlighting branches and merges.

---

2. Filtering Commit History

a. Limit the Number of Commits

To view a specific number of recent commits:

git log -n <number>

Example:

git log -n 5

Shows the last 5 commits.

b. Search by Author

To filter commits by a specific author:

git log --author="<author-name>"

c. Search by Date Range

To filter commits by date:

git log --since=<date> --until=<date>

Example:

git log --since="2023-01-01" --until="2023-12-31"

d. Search by Commit Message

To find commits with a specific keyword in their messages:

git log --grep="<keyword>"

---

3. Using GitHub or GitLab

If your repository is hosted on GitHub, GitLab, or a similar platform, you can view commit history through their web interface:

• Navigate to the repository.
• Click the Commits tab to see a detailed list of all commits.

---

Understanding the Output

Here’s an example of a commit log entry:

commit abcd1234567890
Author: John Doe <[email protected]>
Date:   Mon Dec 11 10:00:00 2023 +0000

    Added user authentication feature

• Commit hash: A unique identifier for the commit.
• Author: The person who made the commit.
• Date: When the commit was made.
• Message: A description of the changes.

---

Best Practices for Commit History

1. Write Descriptive Commit Messages: Clear messages make it easier to understand changes.
2. Keep Commits Atomic: Each commit should focus on a single change or feature.
3. Use Tags for Milestones: Add tags to specific commits to mark versions or releases.

---

Common Issues and Troubleshooting

1. Commit History Seems Incomplete

• Cause: You might be on a branch with limited commits.
• Solution: Use git log --all to view all branches.

2. Cannot Identify Specific Changes

• Cause: Large commits with vague messages.
• Solution: Use git diff with commit hashes to see changes.

3. Too Many Commits Displayed

• Cause: Large repositories with extensive history.
• Solution: Use filters like --since, --author, or --grep.

---

Conclusion

Accessing and interpreting commit history in Git is an indispensable skill for developers. Whether you’re debugging, reviewing contributions, or studying a project’s evolution, the git log command and its variations provide powerful tools to explore commit data. By leveraging filtering options and graphical tools, you can efficiently navigate even the most complex histories.