I've ran git clean -xf to see if that cleaned up my git status and it has not. It's going outside the project folder for some reason and I'm just flustered. It's showing a bunch of files from my desktop, c:/, basically almost everywhere. For more information, see the LICENSE.txt file.I've just added a new git repo on my machine and I've noticed an extremely messy git status. fboender/espy: Uncommitted changes CopyrightĬopyright 2016-2022, Ferry Boender (et al). $ mgitstatus -flatten -c | grep Uncommitted fboender/multi-git-status: Untracked filesįorce color output and flatten the output so we can grep for things: fboender/ansible-cmdb: Needs push (master) fboender/multi-git-status: Uncommitted changes fboender/ansible-cmdb: Uncommitted changes Sort output by repo status while retaining colors: espy: Uncommitted changes Untracked files ansible-cmdb: Needs push (master) Uncommitted changes Untracked files Sort output by repo name while retaining colors:

$ git config -local mgitstatus.ignore true To ignore a repo, set the mgitstatus.ignore git configuration option for that repo to true. $ mgitstatus -e -no-stashes -d 3 /opt/deploy The following command scans three levels deep in /opt/deploy/ and hides repos that are `ok'. To scan deeper (three dirs instead of two) in the current dir: fboender/multi-git-status: Needs push (master) Untracked files The following command scans two directories deep for Git projects and shows their status: no-stashesĭo now show repos that are `ok' (same as -e) Examples no-untrackedĭo not show branches that have untracked files. no-uncommittedĭo not show branches that have unstaged or uncommitted changes. no-upstreamĭo not show branches that need an upstream. no-pullĭo not show branches that need a pull. You can limit output with the following options: -no-pushĭo not show branches that need a push. If a repo has multiple statuses, multiple lines are shown for that repo. If 0, the scan is infinitely deep -flattenįlatten output by only showing one status per line. Wait SEC seconds between each `git fetch' ( -f option) -cįorce color output (preserve colors when using pipes) -d, -depth=2

Warn about dirs that are not Git repositories -eĭo a `git fetch' on each repo (slow for many repos) -throttle SEC Since there are a lot of different states a git repository can be in, mgitstatus makes no guarantees that all states are taken into account. mgitstatus does NOT contact the remote by default. This requires that the local git repo already knows about the remote changes (i.e. you’ve done a fetch), or that you specify the -f option.

Needs pull (BRANCH) if the branch is tracking a (remote) branch which is ahead.

Changes in the branch may otherwise never be pushed or merged.

Needs upstream (BRANCH) if a branch does not have a local or remote upstream branch configured.

Needs push (BRANCH) if the branch is tracking a (remote) branch which is behind.

Untracked files if there are untracked files which are not ignored.

Uncommitted changes if there are unstaged or uncommitted changes on the checked out branch.If DEPTH is 0, the scan is infinitely deep. This can be changed with the -d ( -depth) option. By default, mgitstatus scans two directories deep. Mgitstatus shows uncommitted, untracked and unpushed changes in multiple Git repositories. Show uncommitted, untracked and unpushed changes for multiple Git repos.

Git status ignore untracked