L05 · Give the project one home and a recoverable checkpoint
Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.
Give the project one home and a recoverable checkpoint
Learning time: about 28.8–45.4 active minutes. Choose ONE presentation: the text (about 5.4 minutes, estimated) OR the lesson video (3:50, measured). Then 25–40 minutes of practice and checking (estimated). Do not count both presentations. Setup delays and optional extra study are separate; learner timing has not yet been piloted.
Where you are: Module 3, lesson 1 of 2. Your environment and permissions have been checked. You will now preserve the first agreed project version.
What you will do
Identify the actual working folder, distinguish local and remote history, and make a small inspected commit without including unrelated or private files. Outcome O3.
Teaching
A folder is where your current project files live. A Git repository records chosen versions of those files. A commit is one recorded version with a message and identifier. A branch is a line of work. GitHub can hold a remote copy, but a local commit does not become a remote backup until the appropriate push succeeds. These distinctions explain many misleading “saved” reports.
Use the designated disposable Workshop Launch Kit workspace from setup. Never initialize this exercise inside your employer's project or your whole Documents folder. If setup already created a repository, use it; do not create a nested repository. Before changing anything, establish the current directory, repository root, branch and local changes.
Ask your agent for a read-only check in the current project:
Identify the current directory and, if this is a Git repository, its root, current branch or detached state, latest commit and uncommitted changes. Report configured remote names and whether the intended teaching repository is identifiable, without exposing credentials. Do not initialize, switch branches, stage, commit, fetch, pull, push or modify anything. This is the disposable Workshop Launch Kit project; stop if the location is another project or the scope is unclear.
You can also inspect basic local status yourself. pwd prints the current directory. git status --short --branch shows the branch and changed/untracked files. git log -1 --oneline shows the latest commit if one exists. These commands do not create a repository or upload files. Read their output; a familiar folder name is not enough when several checkouts exist.
If no repository exists, follow the setup card's initialization route inside the confirmed disposable folder. If you see unrelated work, leave it alone and ask for the correct learning location. Do not use reset, clean, force push or a broad automatic staging command to make the view tidy.
Make your first checkpoint small: the intent and approved project brief. Inspect their content before staging those exact files. Staging selects what the next commit will contain. git diff --cached shows staged changes; it does not show every untracked file automatically. A nontechnical learner can ask an agent to explain the diff, but should still check file names, visible values and boundaries.
Worked example
Your status shows changes to PROJECT-BRIEF.md, an unrelated expense file and PROJECT-INTENT.md. The checkpoint needs the two project documents only. A blanket “include everything” instruction would put unrelated content into history. Instead, name the two authorized paths, inspect the staged diff and verify that the expense file remains outside the commit.
After the commit, the agent gives its identifier and message. That proves a local version exists if the command result confirms it. A later push may still fail because the remote is unavailable or the account lacks permission. Report “local checkpoint made; remote copy pending” rather than “backed up everywhere.” Never expose a token to diagnose authentication.
Do it yourself
Inspect your workspace. If the intended files exist and the location is correct, use this bounded instruction:
In the confirmed disposable Workshop Launch Kit repository, prepare a local checkpoint containing only PROJECT-INTENT.md and PROJECT-BRIEF.md. First stop if any unrelated changes are already staged. Show the two documents and check for credentials or personal data. Do not alter either document, include other files, change branches or contact a remote. If the selected files are safe and match the agreed brief, stage only those paths, inspect the staged diff, and commit with message "Record workshop project scope". If a file is missing, identity configuration is incomplete, or the diff contains unexpected content, stop with the specific issue. Report the actual commit identifier, included paths and remaining changes. Do not claim a push occurred.
If your filenames differ, name them explicitly. Do not paste private file content into a public chat. Save the command results or a concise non-sensitive record showing the commit and included files.
Remote sharing is a separate step. Use only your authorized private teaching repository and the verified route from setup. If that route is unavailable, keep the local checkpoint and label remote access pending. It does not satisfy a later cross-device or cross-account handoff test.
Feedback and retry
Pause here. A satisfactory record names the folder, branch, selected paths, commit identifier and remaining changes. It says whether anything was pushed. A clean working tree does not prove that the correct files were committed; inspect the commit's file list too.
For a retry, create a harmless scratch-note.txt containing “temporary learning note.” Make a deliberate small brief correction. Checkpoint only the brief. Verify the scratch note stays untracked. Preserve it until you decide to remove it normally. This tests selective versioning without risking real data.
Check your understanding
Choose an answer and write one sentence explaining why before you read the answers.
- Does a commit upload files to GitHub?
- A. Yes, immediately.
- B. Only for files under 1 MB.
- C. No.
- Does
git diff --cachedshow the proposed commit or all files on your computer?- A. The staged, proposed commit.
- B. All files on your computer.
- C. Only files that changed since yesterday.
- What should happen if the current folder is another active project?
- A. Continue: Git will keep the two projects apart.
- B. Stop, locate the correct teaching workspace and preserve the other project.
- C. Delete the other project's changes to start clean.
Answers
- C. No. A commit records a local checkpoint; sending it to GitHub is a separate step.
- A. The staged, proposed commit.
- B. Stop and locate the correct teaching workspace; preserve the other project.
Summary
Record a small version you understand. Name the local and remote state separately so the next agent knows where the actual work exists.
Sources
GitHub, GitHub flow and authentication, reviewed 8 November 2026. Commands must be checked in the installed Git environment. This lesson's file-selection exercise is original synthetic teaching material.
