Rullst AcademyRullst Academy/Lesson
Git: changes as a team · Lesson 03 / 10

A change small enough to review

The diff should tell the same story as the change request.

Learning paths16 min

Let's discover together

  1. 1

    In author, with a clean status, create fix-boundary using git switch -c fix-boundary. A branch names a line of commits; it is not a backup of unsaved files. Check the branch before editing.

  2. 2

    Copy variants/test_boundary.py into author as LAB.md describes. Run python -m unittest discover -v: the 120 case should fail. In mission.py, replace minutes >= 120 with minutes > 120 and rerun. On macOS/Ubuntu use python3; on Windows use your setup track’s command.

  3. 3

    Git diff shows unstaged changes; git diff --cached shows what is staged for the next commit. Stage files by name: git add mission.py test_boundary.py. Review the staged diff for environment files, personal data and unrelated edits.

  4. 4

    Commit with a message explaining the fix and push the branch to the local remote with git push -u origin fix-boundary. Commit records local history; push transfers commits. Rullst Academy’s file integration sends a confirmed file but does not automatically create this branch workflow or a pull request.

One change, two roles

Download the kit and follow LAB.md in a new folder. Commands here are reading references; the site does not execute them. Use Git Bash on Windows and a terminal on macOS/Ubuntu. Earlier tracks cover Git and Python setup.

git switch -c fix-boundary
python -m unittest discover -v
git diff
git add mission.py test_boundary.py
git diff --cached
My files and GitHub

Edit, download and send your Markdown notebook to GitHub with confirmation. It does not run Git or open pull requests. The kit is the starter; save edits separately.

Official links and next step

✦
YOUR MISSION

Create a branch and a small commit with a test that detects the defect.

Now it's your turn

Discovery workshop

A decision with evidence

mission.py is staged. A later edit to README.md has not been added.
Build your answers and check when you are ready.
A moment to understand

Which diff should you review before committing?

I need a hint

Compare the agreement with the diff and evidence for the current commit.

Loading your journey…

Take it with you

Record the failing/passing test, staged diff and commit hash. Explain one change you left out.

At your own pace

My files and GitHub

Every lesson can become your own record: code, notes or a practice plan. Saving a file to GitHub is optional and does not change your XP.

Student guide

The editor and downloads open when this lesson is available to your account. Check access below or return to the track map.

Checking your access to this lesson…

Rullstpetbot

AI can make mistakes. Check the lesson material.