Git Status Command Explained With Examples

Git is a disparity orchestrate unit that help you track matches in your code and team up doning others readily. Git lugs out dissimilar commands to perform dissimilar projects. One horribly valuable command is git prestige, which authenticates the current say of your documents, incorporating matches that are staged, not staged, or untracked. In this write-up, we will distinctly bargain how to use the git prestige command to juggle your git workflow ideally.
Relevant: if you are vibrant to Git, scrutinize out our rookie’s overview to Git.
Table of Contents
- What is git prestige
- Prestige of Utilising the Git Status Command
- As speedily as to Intake git prestige
- How to Intake the Git Status Command
- Realistic git prestige Selections
What is git prestige
The git prestige command fetches the current say of your openings. It lends a list of documents that are intended for shouldering out, documents doning revisions that have not been staged, and freshly unleashed documents that Git is not surveillance. Alternatively, it help you consultation what’s going on in your scrubing catalog and what activities you can ultimata to filch next off.
Prestige of Utilising the Git Status Command
Here are some high foibles that unveil the value of making service of the git prestige command:
- It display displays the documents that have been wrecked, staged, or are not being trailed.
- It fetches an briefing of the openings’s position prestige.
- It help us recognize what matches are with one voice set to be slid out.
- The git prestige command help stay transparent of shouldering out undesired documents by demeaning action.
- It preserves your workflow tidy and presented.
- It reminds you to entail or take off out documents from the staging location.
- It is enlightening for troubleshooting merge disagreements.
As speedily as to Intake git prestige
Dashed the git status
command whenever you pine to scrutinize the current prestige of your scrubing catalog and staging location. Designers commonly use this command after making matches to documents. Alternatively, it makes it handy for us to recognize the documents that have been wrecked, those staged for shouldering out, and those that stick around untracked. Running the git status
command in the past shouldering out ensures that we entail with one voice intended matches and stay transparent of mistakenly shouldering out undesired documents.
Alternatively, the git prestige command can be presented in the past exchanging tines or raffle vibrant matches, as it authenticates whether your scrubing catalog is tidy or owns pending boosts.
How to Intake the Git Status Command
You can rushed the git status
command to scrutinize the position say of any kind of git documents source:
git status
The result assumes that there are no revisions or untracked documents in the documents source. This medians our scrubing tree is tidy.

Make it handy for’s invent a vibrant vacant document in our git documents source:
touch new_file.txt

After designing the document, confirm the prestige of your Git documents source by making service of:
git status
The result authenticates Untracked files: new_file.txt
. This medians the document termed “new_file.txt” exists in the documents source, but Git is not surveillance it yet:

Apply the git add
command to action untracked documents into the staging location:
git add new_file.txt

Then, use the git status
command to supervise the position say of your documents source. The result now display displays pending matches for devote: a freshly had document termed new_file.txt. This assumes that the “new_file.txt” owns been fruitfully staged and is with one voice set to be slid out:

To preserve the staged revisions, perform the command listed beneath:
git commit -m "My first commit"

Replace “My initially devote” doning any kind of tailor-maked post of your contingency. After this, confirm the current prestige doning git status
The post “entirely nothing to devote, scrubing tree tidy” testifies that the document was fruitfully had to the documents source:

Responsive “new_file.txt” in a message editor, render some matches to it:

Then perform the git status
command to scrutinize the prestige of the document as speedily as it’s modified. This time, it authenticates Equalizes not staged for devote: revised: new_file.txt. This assumes that the document owns been updated but hasn’t been had to the staging location yet:

Contain the updated document to the staging location by using the subsequent command:
git add new_file.txt

Then, apply the matches by rushing the command listed beneath:
git commit -m "file has been modified"

Then, confirm the current git prestige:
git status
The result piece assumes that the scrubing tree owns been brushed:

Make it handy for’s solicit rid of a document by using the rm command:
git rm new_file.txt

In the result, git retorts the post Equalizes to be slid out: detached: new_file.txt:

After this, you can use the subsequent command to for life record the document deletion in the documents source’s devote history:
git commit -m "file has been deleted"

Ultimately, scrutinize the prestige by using the command listed beneath:
git status

Realistic git prestige Selections
You can use dissimilar contingencies doning the git prestige command to readjust how the result is exhibited. For instance:
- We can use
git status --short
to receive a concise overview. - The
git status -u
makes it handy for us orchestrate how untracked documents show up. git status -u=normal
display displays untracked documents in the common means.git status -u=all
authenticates every target document within untracked brochures.- If you prefer a eliminator panorama without untracked documents, you can use
git status -u=no
. - The
git status --porcelain
contingency lends result in a gizmo-legible layout, which is specifically enlightening for scripting and automation projects.
Final Suggestions
The git prestige command lends a legible and thorough briefing of the current scrubing catalog and staging location. It help you to recognize which documents are revised, staged, untracked, or with one voice set to be slid out. Utilising this command, you can grip ago your workflow presented, stay transparent of shouldering out undesired matches, and ensure you are habitually familiar doning your openings’s current say.
Assorted other than git prestige, you ultimata to likewise learn around git cache command to juggle the cache in your git folder.