Fetch vs Pull

git fetch downloads commits and moves remote-tracking branches, never your branches or files. git pull is a fetch plus a merge (or rebase) into the current branch. Push from the laptop, then fetch and look first:

cd ../laptop
# Edit package.json: add a "dev" script that runs node --watch server.js
git commit -qam "Add an npm dev script that restarts on changes"
git push -q
cd ../booknest
git fetch
git status -sb | head -1
git log --oneline main..origin/main
git pull

From ../server/booknest
   dfab226..a2508da  main       -> origin/main
## main...origin/main [behind 1]
a2508da Add an npm dev script that restarts on changes
Updating dfab226..a2508da
Fast-forward
 package.json | 1 +
 1 file changed, 1 insertion(+)

After the fetch main was untouched, one commit behind, and main..origin/main listed what a pull would bring. That pause is the safety: you see what arrived before deciding how to integrate it. A blind pull into a branch with local commits makes a merge commit you may not want; with pull.ff only (First-Time Setup) Git 1,932 instead stops with "Not possible to fast-forward", and you choose git pull --rebase or --no-rebase.