A hands-on guide

Git, without the jargon

Git remembers useful checkpoints in your work. It lets you try ideas on a side path, combine them when you are ready, and recover when something goes wrong.

Try a change How teams share work

Your folder

The work in progress

A checkpoint

A saved version you name

A side path

A safe place to experiment

Git is the version tracker on your computer. GitHub is one place to host a shared copy online. Git works without GitHub, and you can use GitHub without knowing every Git command.

01 · The basic loop

A draft, a shortlist, a checkpoint

Git gives you control over what gets saved. You edit in your project folder, select the changes you want to keep, then make a checkpoint called a commit.

Make one change, then save it

A pretend project. Nothing on your computer is changed.

Your folder

Where you edit

Clean

home.html

The page content

colors.css

How the page looks

Staging list

What goes in the next checkpoint

Nothing selected

Your selection appears here

Checkpoints

Saved moments in the project

Last save: project created

Project created

current point

Nothing is waiting to be saved. Your project folder and its last checkpoint match.

Everyday Git words: status asks what changed; diff shows the edits; add stages selected edits; commit saves the checkpoint.

You do not have to stage every file together. That small pause before a commit helps you leave out an unfinished or unrelated change.

02 · Experiment safely

A branch is a side path

A branch starts from a checkpoint and gives your next commits their own path. You can keep the main version steady while you test a new idea.

Branch playground

The main branch is the shared line of work. Start with a copy of its latest checkpoint.

Repository

The project folder plus the history Git keeps with it.

Commit

A named checkpoint. It records who saved it, when, and why.

Branch

A movable name for one line of work, such as main or try-new-colors.

The branch is not a separate project copy. It is a lightweight pointer to a series of commits. Switch branches to move between lines of work.

04 · When paths meet

A conflict is a question, not a disaster

If two people change different parts of a project, Git can often combine the work automatically. If they change the same part, it pauses so a person can decide what the final version should say.

Maya's branch

The open studio begins at 09:30.

Leo's branch

The open studio begins at 10:00.

Git pauses here

Both people changed the same line. Git cannot know which time is right, so it asks a person to choose or combine them. Neither person's change is silently discarded.

Your resolved version

Choose which wording belongs in the final version.

05 · Recover with care

Undo depends on what you want to undo

Git has several ways to go back. Choose the situation that sounds like yours to see the difference.

What happened?

A matching tool

Revert the checkpoint

Revert makes a new checkpoint that reverses the earlier one. It keeps the shared history intact, which is why it is usually the clearest choice for work other people already have.

git revert <commit>

Usually the safest undo for shared work.

06 · The vocabulary

Words you will see around Git

These are the labels people use for the pieces you just explored. You can understand the workflow before memorising any commands.

Repository: A project folder with Git's saved history attached.
Working folder: The files you are editing right now.
Status and diff: Status says what changed. A diff shows the exact lines that changed.
Staging area (index): A shortlist of edits to include in the next commit. The index is another name you may see for this area.
Commit: A named checkpoint containing a set of project changes.
Branch and main: A branch is a named line of work. Main is a common name for the project's primary line.
HEAD and switch: HEAD points to the commit your current work is based on. Switching branches moves your working folder to that line of work.
Tracked and untracked: Tracked files are already part of Git history. A new file is untracked until you choose to stage it.
Merge: Joining changes from one branch into another.
Remote: A named address for another copy of the repository, often online.
Clone: Making a local copy of a repository and its history.
Push / fetch / pull: Send commits up; check what is new; bring remote changes down and integrate them.
Pull request: A review conversation on GitHub or another hosting service before a merge.
.gitignore: A list of files Git should leave alone, such as temporary files or local settings. It does not remove files already committed, so it is not a way to hide a secret that was saved.
Tag: A fixed name for a specific commit, often used to mark a release such as v1.0.
Fork: A server-side copy of someone else's repository, common when contributing to open-source projects.

07 · Try it yourself

A quick check

Three small questions to see whether the model makes sense. Guessing is part of learning.

Question 1 of 3

Which step chooses edits for your next checkpoint?

Keep building

You can learn Git one checkpoint at a time.

Return to the Coding for Non-Coders guide for project ideas, tools, and practical ways to build with AI.

Back to the guide

Git, without the jargon

Git remembers useful checkpoints in your work. It lets you try ideas on a side path, combine them when you are ready, and recover when something goes wrong.

Your folder

The work in progress

A checkpoint

A saved version you name

A side path

A safe place to experiment

Git is the version tracker on your computer. GitHub is one place to host a shared copy online. Git works without GitHub, and you can use GitHub without knowing every Git command.

01 · The basic loop

A draft, a shortlist, a checkpoint

Git gives you control over what gets saved. You edit in your project folder, select the changes you want to keep, then make a checkpoint called a commit.

Make one change, then save it

A pretend project. Nothing on your computer is changed.

Your folder

Where you edit

Clean

home.html

The page content

colors.css

How the page looks

Staging list

What goes in the next checkpoint

Nothing selected

Your selection appears here

Checkpoints

Saved moments in the project

Last save: project created

Project created

current point

Nothing is waiting to be saved. Your project folder and its last checkpoint match.

Everyday Git words: status asks what changed; diff shows the edits; add stages selected edits; commit saves the checkpoint.

You do not have to stage every file together. That small pause before a commit helps you leave out an unfinished or unrelated change.

02 · Experiment safely

A branch is a side path

A branch starts from a checkpoint and gives your next commits their own path. You can keep the main version steady while you test a new idea.

Branch playground

The main branch is the shared line of work. Start with a copy of its latest checkpoint.

Repository

The project folder plus the history Git keeps with it.

Commit

A named checkpoint. It records who saved it, when, and why.

Branch

A movable name for one line of work, such as main or try-new-colors.

The branch is not a separate project copy. It is a lightweight pointer to a series of commits. Switch branches to move between lines of work.

04 · When paths meet

A conflict is a question, not a disaster

If two people change different parts of a project, Git can often combine the work automatically. If they change the same part, it pauses so a person can decide what the final version should say.

Maya's branch

The open studio begins at 09:30.

Leo's branch

The open studio begins at 10:00.

Git pauses here

Both people changed the same line. Git cannot know which time is right, so it asks a person to choose or combine them. Neither person's change is silently discarded.

Your resolved version

Choose which wording belongs in the final version.

05 · Recover with care

Undo depends on what you want to undo

Git has several ways to go back. Choose the situation that sounds like yours to see the difference.

What happened?

A matching tool

Revert the checkpoint

Revert makes a new checkpoint that reverses the earlier one. It keeps the shared history intact, which is why it is usually the clearest choice for work other people already have.

git revert <commit>

Usually the safest undo for shared work.

06 · The vocabulary

Words you will see around Git

These are the labels people use for the pieces you just explored. You can understand the workflow before memorising any commands.

Repository: A project folder with Git's saved history attached.
Working folder: The files you are editing right now.
Status and diff: Status says what changed. A diff shows the exact lines that changed.
Staging area (index): A shortlist of edits to include in the next commit. The index is another name you may see for this area.
Commit: A named checkpoint containing a set of project changes.
Branch and main: A branch is a named line of work. Main is a common name for the project's primary line.
HEAD and switch: HEAD points to the commit your current work is based on. Switching branches moves your working folder to that line of work.
Tracked and untracked: Tracked files are already part of Git history. A new file is untracked until you choose to stage it.
Merge: Joining changes from one branch into another.
Remote: A named address for another copy of the repository, often online.
Clone: Making a local copy of a repository and its history.
Push / fetch / pull: Send commits up; check what is new; bring remote changes down and integrate them.
Pull request: A review conversation on GitHub or another hosting service before a merge.
.gitignore: A list of files Git should leave alone, such as temporary files or local settings. It does not remove files already committed, so it is not a way to hide a secret that was saved.
Tag: A fixed name for a specific commit, often used to mark a release such as v1.0.
Fork: A server-side copy of someone else's repository, common when contributing to open-source projects.

07 · Try it yourself

A quick check

Three small questions to see whether the model makes sense. Guessing is part of learning.

Question 1 of 3

Which step chooses edits for your next checkpoint?

Keep building

You can learn Git one checkpoint at a time.

Return to the Coding for Non-Coders guide for project ideas, tools, and practical ways to build with AI.

Back to the guide

A draft, a shortlist, a checkpoint

A branch is a side path

Your computer and the shared copy

Clone

A conflict is a question, not a disaster

Undo depends on what you want to undo

Revert the checkpoint

Words you will see around Git

A quick check

Which step chooses edits for your next checkpoint?

You can learn Git one checkpoint at a time.

A draft, a shortlist, a checkpoint

A branch is a side path

Your computer and the shared copy

Clone

A conflict is a question, not a disaster

Undo depends on what you want to undo

Revert the checkpoint

Words you will see around Git

A quick check

Which step chooses edits for your next checkpoint?

You can learn Git one checkpoint at a time.