BeginnerGit & Version Control

Lab: run the git workflow

Decide which git command fits each everyday situation.

Lab · optionalFundamentalsBeginner9 min

Recommended first

Working with remotes

By the end of this lesson you will be able to:

Map everyday tasks to the right git command
Use git status to avoid mistakes
Distinguish fetch from pull

Optional scenario lab. The git lessons were hands-on; this checks that you can reach for the right command under pressure. Try the steps in a real terminal too — that's the best practice of all.

Scenarios: the everyday git loop

1.
You edited a file and want it recorded in your next snapshot. What's the order?
git commit, then git addgit add, then git commitgit push, then git commitgit merge, then git add
2.
About to commit, git status shows a file you didn't mean to stage. What do you do?
Commit anywaygit restore --staged <file> to unstage itDelete the repositorygit push to fix it
3.
You want to try a risky change without disturbing the stable main line. Best move?
Edit main directly and hopeCreate a branch and work thereMake a copy of the whole folderStop using git
4.
What's the difference between git fetch and git pull?
They're identicalpull = fetch + merge; fetch alone only downloadsfetch merges, pull doesn'tfetch deletes local commits

Green across the board? You can drive the core git loop by hand — exactly the self-reliance this module is about.

Finished reading? Mark it complete to track your progress.

Working with remotes

clone, push, pull, fetch — sync your repository with a server like GitHub.

Systems thinking

Stop looking at lines of code and start seeing flows — inputs, outputs, state, and side effects.