Git Without Fear: 7 Commands That Cover 90% of Your Work

The biggest reason people fear Git is that they treat it like a memorisation exam. In reality, daily work uses seven commands. The rest are rare cases you look up when needed.

1) git init / git clone

The beginning. init for a new project, clone for an existing one. Once per project lifetime.

2) git status

The command you will use more than any other. It tells you what changed, what is staged, and what is not. If you are lost — type status.

3) git add -A

Selects the changes that go into the next commit. -A means everything. Do not be afraid of it — it only selects, it does not save.

4) git commit -m "message"

This is the actual save. And the message matters more than you think: in a month you will not remember what you did, you will read the message. Write "what changed and why", not "updates".

Simple rule: if the same message could be written ten times in this project, it is not useful.

5) git push

Sends your commits to the server. Without it everything lives only on your machine — and if the machine dies, it is gone.

6) git pull

Brings the latest changes from the server. Make it a habit: pull before starting new work. It prevents most conflicts.

7) git log --oneline

A list of commits, one line each. The best way to understand what happened in a project and to return to an earlier state when confused.

What nobody tells you

Working with Git needs no server and no account at the start. init, add and commit all work locally. The biggest benefit is being able to return to any earlier version in a second — worth learning on its own.

Start on your first project, not once the project grows. If you wait, you will be trying to recover a history that does not exist, and you will stay afraid to touch any file.