小学生什么时候放假
To 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)

To view Git commit history, use the gitlog command. 1. The basic usage is gitlog, which can display the submission hash, author, date and submission information; 2. Use gitlog--oneline to obtain 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 VSCode.

To delete a Git branch, first make sure it has been merged or no retention is required. Use gitbranch-d to delete the local merged branch. If you need to force delete unmerged branches, use the -D parameter. Remote branch deletion uses the gitpushorigin-deletebranch-name command, and can synchronize other people's local repositories through gitfetch-prune. 1. To delete the local branch, you need to confirm whether it has been merged; 2. To delete the remote branch, you need to use the --delete parameter; 3. After deletion, you should verify whether the branch is successfully removed; 4. Communicate with the team to avoid accidentally deleting shared branches; 5. Clean useless branches regularly to keep the warehouse clean.

The five most valuable stablecoins in 2025 are Tether (USDT), USD Coin (USDC), Dai (DAI), First Digital USD (FDUSD) and TrueUSD (TUSD).

The "Dogcoin" in the currency circle usually refers to newly issued cryptocurrencies with extremely low market value, opaque project information, weak technical foundation or even no practical application scenarios. These tokens often appear with high-risk narratives.

To identify fake altcoins, you need to start from six aspects. 1. Check and verify the background of the materials and project, including white papers, official websites, code open source addresses and team transparency; 2. Observe the online platform and give priority to mainstream exchanges; 3. Beware of high returns and people-pulling modes to avoid fund traps; 4. Analyze the contract code and token mechanism to check whether there are malicious functions; 5. Review community and media operations to identify false popularity; 6. Follow practical anti-fraud suggestions, such as not believing in recommendations or using professional wallets. The above steps can effectively avoid scams and protect asset security.

What are the key points of the catalog? UselessCoin: Overview and Key Features of USELESS The main features of USELESS UselessCoin (USELESS) Future price outlook: What impacts the price of UselessCoin in 2025 and beyond? Future Price Outlook Core Functions and Importances of UselessCoin (USELESS) How UselessCoin (USELESS) Works and What Its Benefits How UselessCoin Works Major Advantages About USELESSCoin's Companies Partnerships How they work together

To add a subtree to a Git repository, first add the remote repository and get its history, then merge it into a subdirectory using the gitmerge and gitread-tree commands. The steps are as follows: 1. Use the gitremoteadd-f command to add a remote repository; 2. Run gitmerge-srecursive-no-commit to get branch content; 3. Use gitread-tree--prefix= to specify the directory to merge the project as a subtree; 4. Submit changes to complete the addition; 5. When updating, gitfetch first and repeat the merging and steps to submit the update. This method keeps the external project history complete and easy to maintain.

This article has selected several top Python "finished" project websites and high-level "blockbuster" learning resource portals for you. Whether you are looking for development inspiration, observing and learning master-level source code, or systematically improving your practical capabilities, these platforms are not to be missed and can help you grow into a Python master quickly.
