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

An agreement before code

A good change starts with a small problem another person can understand.

Learning paths12 min

Let's discover together

  1. 1

    This continuation uses basic Git: status, add, commit and branches. If these are new, take Git: every change counts. Basic Python helps with the small program; the catalog has setup tracks for three systems. HTML and JavaScript are not prerequisites here.

  2. 2

    Our program calculates study minutes. The agreement accepts whole minutes from 1 to 120 and sessions from 1 to 7. The starter deliberately rejects 120. Fixing that boundary is the scope; redesigning everything or adding login is outside it.

  3. 3

    Download the kit and follow LAB.md in a new folder outside important projects. It creates origin.git, author and reviewer only on your computer. Origin is a remote name; it does not necessarily mean GitHub. Use fictional identities in this rehearsal, configured with --local.

  4. 4

    Write in PULL_REQUEST.md: problem, expected behavior, proposed change, test and exclusions. A GitHub issue can record the problem; the local file lets you practice without an external account. Rullst Academy answers assess understanding, not proof of real collaboration.

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 --version
python --version
pwd
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

Define scope, acceptance criteria and an isolated local workshop.

Now it's your turn

Discovery workshop

A decision with evidence

Requirement: accept 120 minutes. A proposal also changes all colors and adds registration.
Build your answers and check when you are ready.
A moment to understand

Which proposal makes review easier?

I need a hint

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

Loading your journey…

Take it with you

Prepare the workshop and write a checkable criterion including 1, 120 and 121. Record the study folder path.

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.