(I have more git repositories than non-git folders, so this is easiest for me). git_checker_ignore in my main "repository" folder, ~/Dev/src-repos/, which lists all The way I've set my stuf up is that I have a.
(Similar to how git automatically ignores files in. If -ignorefile is not given but the current directory contains a file ".git_checker_ignore", this is used as ignorefile.those files that arent in the repository and arent ignored by. You can use -no-recursive command line argument to disable recursive walking (it is then assumed that all "basedirs" are git repositories). Try using git ls-files -other - it should list all files that git doesnt know about i.e.You can provide a -config file with command line args (if you don't want to specify them on the command line).You can provide base-dirs directly at the command line.The script provides for a range of choices based on how you use it: Note: Basedirs are NEVER ignored by glob patterns in ignorefile. ignorefile IGNOREFILE File with directories to ignore (glob patterns). dirfile DIRFILE, -f DIRFILE Instead of listing basedirs on the command line, you can list them in a file. config CONFIG, -c CONFIG Instead of providing command line arguments at the command line, you can write arguments in a yaml file (as a dictionary). This is typically used to prevent the command prompt from closing when executing as e.g. wait If changes are found, wait for input before continuing. This is disabled by default, since it requires making a lot of remote requests which could be expensive. check-fetch Check if origin has changes that can be fetched. no-followlinks -ignore-untracked Ignore untracked files. followlinks Follow symbolic links when walking/scanning the basedirs. no-recursive Disable recursive scanning. recursive Scan the given basedirs recursively. loglevel LOGLEVEL Set logging output threshold level. optional arguments: -h, -help show this help message and exit -verbose, -v Increase verbosity. Basically it just scans recursively, considering all directories with a '.git' subfolder a git repository. A directory can be either (a) a git repository, or (b) a directory containing one or more git repositories. positional arguments: basedir One or more base directories to scan. Using "all" hides all changes to submodules (and suppresses the output of submodule summaries when the config option status.submoduleSummary is set).$ git-status-checker -h usage: git-status-checker ] ] Git status checker script. 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). 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. can be either "none", "untracked", "dirty" or "all", which is the default. Ignore changes to submodules when looking for changes. 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 kommentar(er)
