RE: [help] git status doesn't seem to work.

[<rsbecker@nexbridge.com>]

On December 5, 2024 2:53 PM, 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'.
>
>nothing to commit, working tree clean
>~/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(-) ~/Peeranoia_Framework $ git status

This is exactly what git pull is supposed to do. The operation does not
leave files in an uncommitted state, so the message

>On branch main Your branch is up to date with 'origin/main'.
>nothing to commit, working tree clean

is 100% correct before and after the pull in your example.