Showing staged and unstaged changes in Git
In this article, we will see how to show the changes we have staged for the next commit and the changes we have not yet staged. There are two commands we can run in Git to show the staged changes.
Let's start with the basics.
Use git statusto display changes
We run git statusthe command to display the status of our working directory. This command displays the staged and untracked files in our working directory.
We use the command with --verbosethe -d flag git statusto display the staging files. --verboseThe options are -vthe same as for -d.
$ git status -v
As shown above, -vthe options show staged files and file content changes.
Use git diffto display changes
We use git diffthe command to show the changes between the staging area and the working directory. You can run the command with --cachedthe - flag git diffto show HEADthe changes between the staging area and .
git diff --cached
We can run the command with --name-only --cachedthe -d flag git diffto display only the file names.
$ git diff --name-only --cached
README.md
git diff --cachedgit diff --stagedSynonymous with command.
We can run the command with HEADto git diffshow both staged and unstaged changes. Let's look at an example.
We will run git statusthe command to check the status of our working directory.
As shown above, we have one modified README.mdfile ready to commit and one modified downloadpdf.phpfile not yet ready to commit. You can view the changes to these two files in the following way.
git diff HEAD
You use git statusthe -d command to show staged and unstaged changes. Just -vvadd the -d flag to the command as shown below.
$ git status -vv
The benefit of using the above command is that it tells you which file is staged and which files are not staged for commit.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Git installation and establishment of local warehouse service
Publish Date：2025/04/05 Views：89 Category：Git
-
Git is a distributed version control system: the client does not only extract the latest version of the file snapshot, but also completely mirrors the original code repository. It has the following advantages: a. Since every extraction oper
git remote operation——multiple remote repositories for one project
Publish Date：2025/04/05 Views：131 Category：Git
-
Multiple remote repositories for a git project In our git project, the command to operate the remote repository information is $ git remote # 查看当前所有的远程仓库的名称 $ git remote -v # 查看远程仓库的名称和远程仓
Git cherry pick command usage
Publish Date：2025/04/05 Views：190 Category：Git
-
git cherry-pick is a powerful command that allows us to select an arbitrary Git commit by reference and attach it to the HEAD of the current working branch. Cherry picking is the act of picking a commit from one branch and applying it to an
Comparison between Git merge and Git rebase
Publish Date：2025/04/05 Views：171 Category：Git
-
The git rebase command may seem like Git wizardry to beginners, but if used carefully, it can actually make life easier for your development team. In this article, we compare git rebase with the related git merge command and identify all th
How to fix Git error Error: src refspec master does not match any
Publish Date：2025/04/05 Views：124 Category：Git
-
When using Git, we may encounter the error "src refspace master does not match any". Here's what the error means and how to fix it. What does src refspec master does not match any Mean in Git mean? We may encounter this error when we try to
Rebase local branch when pulling changes from remote repository branch in Git
Publish Date：2025/04/05 Views：144 Category：Git
-
This article will cover the basics of rebasing your local branch when pulling changes from a remote repository branch in Git. We use the version control system Git to track changes made to files. We commit changes in a local branch in our l
Undo Git Stash
Publish Date：2025/04/04 Views：187 Category：Git
-
This article explains how to make and save changes to a repository. Git allows you to save changes locally and push them to a server when needed. In Git, we don't use the term save , but commit . We use git add , git commit , and git stash
View a list of cache entries in Git
Publish Date：2025/04/04 Views：59 Category：Git
-
We often need to pause our work and focus on something else in our development environment. Therefore, we may need to temporarily save our current work and focus on a different one. We may want to resume our original work later. git stash T
Git stores specific files
Publish Date：2025/04/04 Views：115 Category：Git
-
This article will cover storing changes to only specific files in Git. In Git, when we make some changes in our working tree, we may have some changes which may or may not be staged in our local repo. We may now wish to save these changes f
