For all unstaged files in current working directory use:
git checkout -- .
For a specific file use:
git checkout -- path/to/file/to/revert
-- here to remove ambiguity (this is known as argument disambiguation).
For Git 2.23 onwards, one may want to use the more specific
git restore .
git restore path/to/file/to/revert
that together with
git switch replaces the overloaded
git checkout (see here), and thus removes the argument disambiguation.
git-clean - Remove untracked files from the working tree
git clean [-d] [-f] [-i] [-n] [-q] [-e <pattern>] [-x | -X] [--] <path>…
Cleans the working tree by recursively removing files that are not under version control, starting from the current directory.
Normally, only files unknown to Git are removed, but if the
-x option is specified, ignored files are also removed. This can, for example, be useful to remove all build products.
If any optional
<path>... arguments are given, only those paths are affected.
Step 1 is to show what will be deleted by using the
# Print out the list of files and directories which will be removed (dry run)
git clean -n -d
Clean Step - beware: this will delete files:
# Delete the files from the repository
git clean -f
- To remove directories, run
git clean -f -d or
git clean -fd
- To remove ignored files, run
git clean -f -X or
git clean -fX
- To remove ignored and non-ignored files, run
git clean -f -x or
git clean -fx
Note the case difference on the
X for the two latter commands.
clean.requireForce is set to "true" (the default) in your configuration, one needs to specify
-f otherwise nothing will actually happen.
Again see the
git-clean docs for more information.
If the Git configuration variable clean.requireForce is not set to
false, git clean will refuse to run unless given
Don’t use the standard ignore rules read from .gitignore (per
$GIT_DIR/info/exclude, but do still use the ignore
rules given with
-e options. This allows removing all untracked files,
including build products. This can be used (possibly in conjunction
with git reset) to create a pristine working directory to test a clean
Remove only files ignored by Git. This may be useful to rebuild
everything from scratch, but keep manually created files.
Don’t actually remove anything, just show what would be done.
Remove untracked directories in addition to untracked files. If an
untracked directory is managed by a different Git repository, it is
not removed by default. Use
-f option twice if you really want to
remove such a directory.
Update: as mentioned below by toupeira, you can use the
--porcelainoption of git status (since commit 6f15787, September 2009, git 1.7.0).
I mentioned in my answer "What does the term porcelain mean in Git?" that:
However, that won't show the ahead/behind information: see "What to add to “git status --porcelain” to make it behave like “git status”?": for that, you would still need to use other commands: see "How to know if git repository has changes that have not been synchronized with server?"
Initial answer March 2009
In porcelain command, a:
gives you the changes since the last commit (what you would be committing if you run "git commit -a").
A possible equivalent in plumbing command would be:
for listing all modified (working directory or index) files
If you create your repository by cloning someone else's repository, the remote "master" branch is copied to a local branch named "origin". You get your own "master" branch which is not tied to the remote repository.
There is always a current head, known as HEAD. (This is actually a symbolic link, .git/HEAD, to a file like refs/heads/master.)
run "git status" and analyze the output:
More details in the SO question "Why is Git telling me “Your branch is ahead of ‘origin/master’ by 11 commits.” and how do I get it to stop?"
Possible equivalent in plumbing command:
for listing all commits, but requires analyzing the output as well...
Again, git ls-files could be used to produced the same result than a git status.