On Thu, Dec 05, 2024 at 07:52:37PM +0000, A bughunter wrote: > [help] git status doesn't seem to work. See how a pull caused updates after status showed "up to date" > > ``` > ~/Peeranoia_Framework $ git status > On branch main > Your branch is up to date with 'origin/main'. This is comparing your branch with the local tracking branch we have, refs/remotes/origin/main. It doesn't touch the network, and that tracking branch is essentially a cache of the last value we fetched. > ~/Peeranoia_Framework $ git pull > Enter passphrase for key '/data/data/com.termux/files/home/.ssh/id_ed25519': > remote: Enumerating objects: 17, done. > remote: Counting objects: 100% (17/17), done. > remote: Compressing objects: 100% (15/15), done. > remote: Total 15 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0) > Unpacking objects: 100% (15/15), 6.41 KiB | 312.00 KiB/s, done. > From github.com:freedom-foundation"up to date"/Peeranoia_Framework > 03edf66..4cf4f51 main -> origin/main > Updating 03edf66..4cf4f51 > Fast-forward > README.md | 24 +++++++++++++++++++++--- > 1 file changed, 21 insertions(+), 3 deletions(-) This pull is doing a fetch under the hood (since pull is essentially "fetch + merge"). It updates the tracking branch origin/main, at which point a "git status" would show that your local branch is not up to date. But since it then immediately merges the result, you find that afterwards: > ~/Peeranoia_Framework $ git status > On branch main > Your branch is up to date with 'origin/main'. ...your branch is now up to date. This is all working as expected. If you want a more up-to-date view of "origin/master" when you run your "git status", try "git fetch" to hit the network first. You might also find more information in: https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches -Peff
