They do two different things . Let say , you did GIT PULL and then started editing some files and probably have added and commited those changes to the be pushed … and then for some reason you decided to just discard all the changes that have been made to the given files and go … Read more
Git normally doesn’t clean ignored files unless the -x flag is specified, but strangely it cleans out when configured as you did (folder/*). As @VonC pointed out, you should change your .gitignore-file to ignore the directory (data/) rather than its contents (data/*). It’s a subtle difference, but it matters to git.
The difference is the capital X you’re using. Use a small x instead of the capital one. Like in: git clean -x. git clean -x -n -e local_settings.py # Shows what would remove (-n flag) git clean -x -f -e local_settings.py # Removes it (note the -f flag) From the git documentation: -x Don’t use … Read more
I just faced the same issue and solved it using the following.First clear tracked files by using : git clean -d -f then try git pull origin master You can view other git clean options by typing git clean -help
Git doesn’t track directories, so it won’t remove ones that become empty as a result of a merge or other change. However, you can use git clean -fd to remove untracked directories (the -fd flag means force removal of untracked files and directories).
No. Those files are gone. (Just checked on Linux: git clean calls unlink(), and does not backup up anything beforehand.)
Update Feb. 2021, eleven years later: the new git maintenance command (man page) should supersede git gc, and can be scheduled. Original: git gc –aggressive is one way to force the prune process to take place (to be sure: git gc –aggressive –prune=now). You have other commands to clean the repo too. Don’t forget though, … Read more
You can run these two commands: # Revert changes to modified files. git reset –hard # Remove all untracked files and directories. # ‘-f’ is force, ‘-d’ is remove directories. git clean -fd