git-rm

问题 The documentation for git-rm contains this short description: git-rm - Remove files from the working tree and from the index What exactly is meant by the working tree and the index, and which local or remote files will be removed? 回答1: The "working tree" is your checkout of the files sitting on disk. The "index", "staging area", or "cache" (you'll see it referred to as all three) is internal to Git. It's the space you prepare the next commit. When you git add you're copying the files from the

问题 I want to remove an entire directory with GIT ... each time I keep getting the same error and don't understand why this is happening. I want to remove the "blue_white" folder ... ├── css │ ├── design.css │ └── red_white.css ├── images │ ├── blue_white │ │ ├── accordion-button.png │ │ ├── accordion-shadow.png │ │ ├── button1.png │ │ ├── oem-slide-shadow.png │ │ └── truncate-arrow.png │ └── red_white │ ├── accordion-shadow.png └── pages.xml When I do this ... git rm -r blue_white/ I get this ..

问题 There are several very related question already on stackoverflow (a few are linked below) but I could not solve my particular problem. I share a repository with Co-workers who have pushed huge datafiles/images that increased the size of the remote repository up to 14 GB. Later on, these files got deleted using just rm filename which resized the local repositories to a reasonable size. However, when I check online, the repository's size is still 14 GB. What I tried to reduce the repositories

问题 I am learning Git and am unable to understand under what condition the -f flag is used while issuing the "git rm" command. Please explain a scenario where rm -f would be required instead of rm only? 回答1: Explanation: The -f is used to remove a file if the file is not up to date with your last checked out commit. It is to prevent you from removing a file that you have made changes to, but have not yet checked them in. Example: You check out commit 0a12d4 that contains the file sample.txt .

问题 On my local machine I removed files from folder. git init git add --all then I wrote (don't ask me, why! :) ) git rm -rf I don't commit, yet. Now I have empty folders in my project. In .git folder has objects with 53 Mb of files. How can I recover my files? I've tried programs like Drill Disc and Stellar, but not found my files. And I can't rollback from GIT. How can I recover the lost files? 回答1: (update) Use git fsck instead, it is a builtin command for retrieving files you have once added

问题 I accidentely said git rm -r . . How do I recover from this? I did not commit. I think all files were marked for deletion and were also physically removed from my local checkout. EDIT: I could (if I knew the command) revert to the last commit. But it would be a lot better if I could just undo the git rm -r . . Because I am not really sure what I did after the last commit and before the git rm -r . . 回答1: git reset HEAD Should do it. If you don't have any uncommitted changes that you care

问题 I just tried to checkout my master branch and ran into: error: Untracked working tree file 'app.xcodeproj/project.xcworkspace/xcuserdata/u.xcuserdatad/UserInterfaceState.xcuserstate' would be overwritten by merge. So, I tried to delete this file from git (I'd already added an expression in .gitignore to catch it) using: git rm --cached app.xcodeproj/project.xcworkspace/xcuserdata/u.xcuserdatad/UserInterfaceState.xcuserstate and got: fatal: pathspec 'app.xcodeproj/project.xcworkspace

问题 Need help figuring out a couple common workflows with Github. I come from a VS TFS background, so forgive me. Undoing Pending Changes Let's say I have cloned of a git repository to my local file system. At this point, the project's local files match exactly what's in the remote repoistory. Then I decided to make some changes to the code, and change the local versions of a couple files. After doing some testing, I figure out that I want to discard my local changes and revert the local files

问题 I do not understand the difference between git rm --cached and git update-index --assume-unchanged . I'm aware that git rm --cached <file> will remove a file from the staging area. And, I know that git update-index --assume-unchanged <file> also does this. I've also seen both commands offered as suggestions to similar questions here on SO. Is there another affect of either of these two commands that makes them different? 回答1: The command git rm --cached <file> is used to untrack files in a

问题 I was using git for the first time, I had a directory with several programs written in it and did the following steps I did git add . then git commit , then it i got a message Aborting commit due to empty commit message. Then i thought, let me commit group of files under common message. So i thought of removing all the added files. So i did git rm -r -f When i do a ls i have lost all my code. Is there any way that i can get them back, to my foolishness i don't have backup copy even. Things