Shows repo Ok when repo needs pull about multi-git-status

[fboender]

Very strange. It's working fine for me:

fboender @ jib ~/Projects/fboender/test_gogs (master) $ git status
On branch master
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)

nothing to commit, working tree clean

fboender @ jib ~/Projects/fboender $ mgitstatus test_gogs/ 1
test_gogs/: Needs pull (master) 

It might have something to do with that extra info in your git status output (the ✔ ~/repo/nagios [master ↓·3|✔]).

On line 25 of the mgitstatus script, there's a DEBUG=0 line. Can you try changing that to DEBUG=1 and pasting the output here?

[drahamim]

Different Repo but same git style

/Users/drahamim/repo/ansible-playbooks
CNT_AHEAD_BEHIND: 0 0
CNT_AHEAD: 0
CNT_BEHIND: 0
REV_LOCAL: a759ec538acdfa82296fb6658c87fedf202d0a58
REV_REMOTE: a759ec538acdfa82296fb6658c87fedf202d0a58
REV_BASE: a759ec538acdfa82296fb6658c87fedf202d0a58
/Users/drahamim/repo/ansible-playbooks: ok 
✔ ~ 
14:25 $ cd repo/ansible-playbooks/
✔ ~/repo/ansible-playbooks [master|✔] 
14:26 $ git status
On branch master
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)

nothing to commit, working tree clean
✔ ~/repo/ansible-playbooks [master ↓·1|✔] 
14:26 $ repostat 
~/repo/ansible-playbooks
CNT_AHEAD_BEHIND: 0 1
CNT_AHEAD: 0
CNT_BEHIND: 1
REV_LOCAL: a759ec538acdfa82296fb6658c87fedf202d0a58
REV_REMOTE: 5b3e3ed4d57a7522b2f5ad282e1cbe28e85ad416
REV_BASE: a759ec538acdfa82296fb6658c87fedf202d0a58
~/repo/ansible-playbooks: Needs pull (master) 
✔ ~/repo/ansible-playbooks [master ↓·1|✔] 
14:27 $ 

[fboender]

It looks as though an automatic "git fetch" is being done somewhere.

When you change into the directory, there are no changes according to your prompt. After having run git status, there's suddenly a new commit:

$ cd repo/ansible-playbooks/
✔ ~/repo/ansible-playbooks [master|✔] 
# git status executed here
✔ ~/repo/ansible-playbooks [master ↓·1|✔] 

I think this might be the problem. mgitstatus doesn't do a "git fetch" on repos, so it doesn't know about the latest remote changes. Apparently your git does a "git fetch" when you run "git status", so as soon as you do so, new remote commits become visible and mgitstatus output changes.

This could either be default behaviour in newer versions of git (my version doesn't do it), or your "git status" command might have been aliased to "git fetch && git status" in your ~/.gitrc or something.

[fboender]

I've implemented an argument (-f) that performs a "git fetch" on each repo before showing the status. This should mimic your setup more closely. Can you check to see if specifying the "-f" option makes the weirdness disappear?

[drahamim]

/Users/drahamim/repo/nagios: ok 
/Users/drahamim/repo/multi-git-status: ok 
✔ ~ 

13:43 $ cd repo/nagios/
✔ ~/repo/nagios [master|✔] 
13:43 $ git status
On branch master
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)

nothing to commit, working tree clean

✔ ~/repo/nagios [master ↓·1|✔] 
13:43 $ repostat
/Users/drahamim/repo/nagios: Needs pull (master) 
/Users/drahamim/repo/multi-git-status: ok 

✔ ~/repo/nagios [master ↓·1|✔] 
13:43 $ cat ~/.bash_profile |grep repostat
./repostat ~/repo 1 -f
alias repostat="~/repostat ~/repo 1 -f"

✔ ~/repo/nagios [master ↓·1|✔] 
13:44 $ ls -al ~/repostat 
lrwxr-xr-x  1 drahamim  staff  32 Oct 29 09:20 /Users/drahamim/repostat -> repo/multi-git-status/mgitstatus
✔ ~/repo/nagios [master ↓·1|✔] 

[fboender]

alias repostat="~/repostat ~/repo 1 -f"

The order here is wrong. This shouldn't even be working. Can you try without the aliases, bash plugins, etc? It's only confusing things. Update to the latest version of multi-git-status (git pull --rebase in the repo) and then run:

$ bash --noprofile --norc
$ /Users/drahamim/repo/multi-git-status -f /Users/drahamim/repo/

[drahamim]

When testing the way you provided above it does execute fetch correctly.
This is the git version I have

git --version
git version 2.17.1 (Apple Git-112)```

[fboender]

Okay, so it seems the problem isn't with multi-git-status, but rather with your git setup. This confirms that:

$ cd repo/ansible-playbooks/
✔ ~/repo/ansible-playbooks [master|✔] 
$ git status
....
✔ ~/repo/ansible-playbooks [master ↓·1|✔] 

You've probably got a git alias in ~/.gitconfig or a shell alias in ~/.bashrc that does a git fetch whenever you do a git status, which is why the new commits are suddenly showing up after running git status.

The easiest thing to do is to keep using the -f option of mgitstatus so that output will be consistent with manually doing git status in your repos.