How do I view the commit history of my Git repository?
Jul 13, 2025 am 12:07 AMTo view Git commit history, use the git log command. 1. The basic usage is git log, which can display the submission hash, author, date and submission information; 2. Use git log --oneline to get a concise view; 3. Filter by author or submission information through --author and --grep; 4. Add -p to view code changes, --stat to view change statistics; 5. Use --graph and --all to view branch history, or use visualization tools such as GitKraken and VS Code.
To view the commit history of your Git repository, you can use the git log
command. It's the most straightforward and commonly used method to see who made changes, when they were made, and what the changes were about.
Basic Usage: git log
Running git log
in your terminal (from within your Git repo directory) will show a list of all commits in reverse chronological order — starting with the most recent.
Each entry includes:
- Commit hash (a unique ID for that commit)
- Author name and email
- Date of the commit
- Commit message
Example:
git log
If your history is long, it'll open in a pager (like less
). You can scroll using arrow keys and press q
to exit.
For a more compact view:
git log --oneline
This shows each commit in a single line, making it easier to scan through.
Filter by Author or Message
Sometimes you're only interested in specific commits — like those made by a certain person or related to a feature or bugfix.
Use:
git log --author="John"
Or search by commit message:
git log --grep="fixed login"
You can combine both filters:
git log --author="John" --grep="login"
These are handy when troubleshooting or reviewing past work.
View Changes in Each Commit
If you want to see not just the metadata but also the actual code changes, add the -p
flag:
git log -p
This shows the "patch" — which lines were added or removed in each commit.
For a summarized version showing how many files changed and line counts:
git log --stat
This helps understand the scope of each change without diving into every diff.
Visualizing History in Branches
If your project has multiple branches, you might want to see how commits are distributed across them.
Try:
git log --graph --oneline --all
This gives a simple text-based graph showing branch merges and divergences.
Alternatively, use tools like:
- GitKraken (GUI tool)
- VS Code built-in Git viewer
-
gitk
(comes with Git)
They provide a visual way to explore complex histories.
So that's how you can look at your Git commit history — from basic logs to filtered views and visual tools. Not too bad once you know the right commands.
The above is the detailed content of How do I view the commit history of my Git repository?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

When you open PyCharm for the first time, you should first create a new project and select a virtual environment, and then be familiar with the editor area, toolbar, navigation bar, and status bar. Set up Darcula themes and Consolas fonts, use smart tips and debugging tools to get more efficient, and learn Git integration.

Social security number verification is implemented in PHP through regular expressions and simple logic. 1) Use regular expressions to clean the input and remove non-numeric characters. 2) Check whether the string length is 18 bits. 3) Calculate and verify the check bit to ensure that it matches the last bit of the input.

The steps to effectively use graphical tools to compare the differences in Git versions include: 1. Open GitKraken and load the repository, 2. Select the version to compare, 3. View the differences, and 4. In-depth analysis. Graphical tools such as GitKraken provide intuitive interfaces and rich features to help developers understand the evolution of code more deeply.

The gitstatus command is used to display the status of the working directory and temporary storage area. 1. It will check the current branch, 2. Compare the working directory and the temporary storage area, 3. Compare the temporary storage area and the last commit, 4. Check untracked files to help developers understand the state of the warehouse and ensure that there are no omissions before committing.

Configuring VSCode to synchronize code with GitHub can improve development efficiency and team collaboration. First, install the "GitHubPullRequestsandIssues" and "GitLens" plugins; second, configure the GitHub account; then clone or create a repository; finally, submit and push the code to GitHub.

To develop a complete Python Web application, follow these steps: 1. Choose the appropriate framework, such as Django or Flask. 2. Integrate databases and use ORMs such as SQLAlchemy. 3. Design the front-end and use Vue or React. 4. Perform the test, use pytest or unittest. 5. Deploy applications, use Docker and platforms such as Heroku or AWS. Through these steps, powerful and efficient web applications can be built.

Verifying an IMEISV string in PHP requires the following steps: 1. Verify the 16-bit numeric format using regular expressions. 2. Verify the validity of the IMEI part through the Luhn algorithm. 3. Check the validity of the software version number. The complete verification process includes format verification, Luhn checking and software version number checking to ensure the validity of IMEISV.

Create tags on remote repository using gitpushorigin, delete tags using gitpushorigin--delete. The specific steps include: 1. Create a local tag: gittagv1.0. 2. Push to remote: gitpushoriginv1.0. 3. Delete local tag: gittag-dv1.0. 4. Delete remote tag: gitpushorigin--deletev1.0.
