Using "all" hides all changes to submodules (and suppresses the output of submodule summaries when the config option status.submoduleSummary is set). Using "dirty" ignores all changes to the work tree of submodules, only changes to the commits stored in the superproject are shown (this was the behavior before 1.7.0). When "untracked" is used submodules are not considered dirty when they only contain untracked content (but they are still scanned for modified content). the same as specifying normal), to help you avoid forgetting to add newly created files.Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree. So if those files aren't in Git's index now, they probably. Git makes new commits from its index, not from your work-tree. Commits of course contain files, so whatever files are in the commits that go in, are inbut an untracked file is by definition a file that is not currently in Git's index. Using "none" will consider the submodule modified when it either contains untracked or modified files or its HEAD differs from the commit recorded in the superproject and can be used to override any settings of the ignore option in git-config or gitmodules. When -u option is not used, untracked files and directories are shown (i.e. The git push command pushes commits, not files. can be either "none", "untracked", "dirty" or "all", which is the default. In some repository directories there are a ton of untracked files that I dont want to delete or add to. It could be due to the detached HEAD in your submodule branch. By default, git will not show files within directories that are untracked. From within your working copy root, it will automatically add the directory and other files and directories within that directory as well. If it doesn't work with the pathname, try the file name. This is likely because your basefldr\subfldr\ directory is untracked, if you run: git add basefldr\subfldr\. Ignore changes to submodules when looking for changes. Is it possible to configure the github desktop client to show only files that are in the repo, same as what gitk seems to do by default, or similar to running git status -untracked-filesno from the command line. In case you actually didn't want to update the submodules and want to revert to the original state, you might want to run git submodule update -force. Path = bundle / fugitive url = git :// / tpope / vim - fugitive.git ignore = dirty Method 2: switch –ignore-submodules=dirtyĪnother method is to use the swicth -ignore-submodules=dirty of git status (available from git version 1.7.2) and create an alias to shorten the typing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |