要查看暫存區(qū)與最後一次提交之間的差異，可使用git diff --cached或git diff --staged命令。 1. 該命令直接比較暫存區(qū)與最新提交（HEAD），僅顯示已添加但未提交的更改；2. 輸出採(cǎi)用標(biāo)準(zhǔn)補(bǔ)丁格式，包含文件名、刪除行（-）、新增行（ ）及上下文行（空格）；3. 若無任何暫存更改，則無輸出；4. 常用於提交前確認(rèn)更改是否正確，尤其適用於多文件或部分更改的場(chǎng)景；5. 可通過選項(xiàng)自定義輸出，如--stat顯示摘要、-w忽略空白符、指定提交哈希對(duì)比特定版本；6. 雖然GUI工具也支持查看，但掌握命令行方式更為通用可靠。

If you want to see the differences between what's currently in your staging area (also known as the index) and your last commit, Git gives you a straightforward way to do that. This is useful when you've added changes to the staging area with git add , and you want to double-check exactly what you're about to commit.

Use git diff --cached to Compare Staged Changes and Last Commit

The most direct command for this is:

 git diff --cached

Or its synonym:

 git diff --staged

Both commands show you what has been staged (added to the index) but not yet committed. It compares your staging area with the latest commit ( HEAD ). This helps confirm whether the changes you're ready to commit are exactly what you intended.

For example, if you edited three files but only ran git add on two of them, git diff --cached will show you only those two files' changes — the ones you're actually about to commit.

Pro tip: If you're used to using git diff without any arguments, note that it shows you unstaged changes only. So don't confuse the two.

What You'll See in the Output

When you run git diff --cached , Git outputs a standard patch-style diff for each file you've staged. The output includes:

• File names involved
• Lines removed (marked with - )
• Lines added (marked with )
• Context lines around changes (marked with space)

This format is very readable and familiar to most developers. If you've made no staged changes at all, the command simply returns nothing — which means your staging area matches the last commit.

Some common scenarios where this comes in handy:

• Before running git commit , to make sure you didn't accidentally stage something you didn't mean to.
• After staging multiple files or partial changes, to verify correctness.
• When working with others and needing to review exactly what's being committed before pushing.

Customize the Output Format (Optional)

If you prefer a different view, Git allows some customization. For instance:

• To get a brief summary instead of full diffs:

   git diff --cached --stat

• To ignore whitespace changes:

   git diff --cached -w

• To compare against a specific previous commit instead of HEAD :

   git diff --cached <commit-hash>

  These options let you tailor the diff output to fit your current needs.

  Also, if you use a GUI Git client or an IDE like VS Code, many of them have built-in views for staged changes. But knowing how to check via the command line ensures you can always verify, regardless of tools available.

  ---

  基本上就這些。

  以上是我如何看到分階段區(qū)域與最後一個(gè)提交之間的差異？的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！