> Is it though? Yes, yes it is. origin/master is not saying that the remote has/hasn't changed. It's comparing your local copy of origin/master, not giving yo

> Is it though? Yes, yes it is. origin/master is not saying that the remote has/hasn't changed. It's comparing your local copy of origin/master, not giving you the status about if remote has/hasn't changed. You need to explicitly ask if remote/origin/master has changed or not if you want to know. Which in your analogy would be like if the store forgot to actually ask the bank if the customer had the money or not, and instead relying on whatever information they have "cached" in the store. Instead, the store has to first ask the bank (remote) if there is any changes. I do agree that it could be worded better to actually help the user understand, as it seems to be a common misconception. Sidenote: I'd be driven to absolute insanity if `git status` started doing remote requests to check the remote origin/master status each time I invoked it.