Save, Checkpoint, Backup and GitHub
Separate four ideas that are easy to confuse when an assistant says it saved your work.
Look around. Try a small click.
This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.
What will make more sense
- Distinguish a saved file from a Git checkpoint.
- Distinguish Git from GitHub and a backup arrangement.
One idea to keep
Ask whether the work was saved, recorded, shared or backed up.
The short lesson
Read the explanation at your pace
The word saved can hide several different actions. A file can be saved on your computer without being recorded in Git. A Git checkpoint can exist locally without being uploaded. An uploaded project can still lack a suitable backup plan. Learning these differences lets you ask your assistant a clearer question when it reports that a task is finished.
Save writes the current editor contents to a file. That is the version you open from the folder afterward. A Git commit records the selected staged content in local project history. In a simple beginner workflow, you review a small edit and record it as a checkpoint. These are related actions, but saving a sentence does not automatically create a new Git checkpoint.
A backup is a separate recovery arrangement for the information you need. Its usefulness depends on where it is stored, what it includes and whether you can recover from it. A project history that lives only on a laptop can disappear with that laptop. A remote repository may help preserve committed files, but it does not automatically cover your other business records or every unsaved change.
GitHub is one service that can host Git repositories online. Git is the version-history system. You can use Git locally without a GitHub account. If you later choose online hosting, its account, access settings and sharing steps deserve a separate decision. The existence of a GitHub button in an editor is not a reason to publish a private customer folder.
Consider our service example. You save a clearer booking sentence. You review and commit that change locally. Later, you decide whether an approved remote should receive it. Independently, your business maintains a backup covering the appropriate records. Four different questions have been answered: what is on disk, what is in history, what was shared and what can be recovered.
The browser activity asks what happened when the assistant only saved service-after.md. The answer is deliberately modest: the file was saved. You have not been told that a commit, upload or backup occurred. Ask the assistant to name the actual action and report its result. Clear words are easier to trust than a broad everything is safe message.
Try it here
What did saved actually mean?
Explore the prepared example, then choose a response. Your choice reveals its explanation immediately.
This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.
The assistant says it saved service-after.md. What can you conclude?
A tiny next step, if you want one
Optional: try 2 small actions at your own pace
You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.
- Optional: read the four definitions in review-checklist.md.
- Optional: look for the Save option in the File menu, without making changes.
A quick confidence check
These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.
Your place is saved in this browser when storage is available. There is no grading or account sync.
Try a short question
Choose an answer to see why it fits. You can try again or explore every explanation.
Does a local commit automatically upload the project?
Is Git the same thing as GitHub?
If something looks different
An assistant says the project is secure because it made a commit.
Ask it to separate local history, access control and backup. A commit alone does not establish those other outcomes.
Sources and further help
Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.