prompt color updating incorrectly? (with my current workflow) about posh-git HOT 2 CLOSED

I need to write up some documentation on this, but roughly...

For branches that aren't configured to track a remote branch, you will only see the default branch color (cyan). For branches that are, the color depends on where the branch sits relative to the remote ref (as shown by git branch -v):

• Default (cyan) = Local branch matches remote tracked branch
• Behind (red) = Remote has commits that local branch doesn't - need to merge/rebase before push
• Ahead (green) = Local branch is up-to-date and has commits that remote doesn't - can safely push

What I believe you're seeing is a common issue with git pull: the git pull <remote> <branch> form of the command doesn't actually update the <remote>/<branch> ref in your local repository. If you look at gitk --all or git log --oneline --decorate --graph --all before and after such a pull, you will notice the origin/master ref doesn't actually move, but your branch will have the new commits (either via merge or rebase). git remote update (or git fetch), on the other hand, do update the remote ref, thus fixing the prompt.

You should see the expected behavior if you use git pull or git pull <remote> instead.

from posh-git.

Ok, I'll give that a try. Thanks for your feedback.

from posh-git.