Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1git add main.py | Agit add . | |
| 2git commit -m "Add login check" | BStages the changes in main.py so they are included in the next snapshot | |
| 3Stage every changed file in the folder so all of them go into the next snapshot | CThe message is vague. It does not explain what changed, so the project history is hard to understand later. | |
| 4A clear commit message says what changed, written in a short present-tense phrase | DSaves a snapshot of the staged files in the repository history with a message | |
| 5git commit -m Add login check | Egit commit -m "Fix score calculation bug" | |
| 6git commit -m "stuff" | FThe message is not wrapped in quotes, so git reads Add, login and check as separate arguments instead of one message. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
git commit -m "message" — Records a snapshot of the files you staged with git add, saving it in the repository history with a short message that explains what changed.git add main.pygit add main.py
git commit -m "Add login check"git commit -m "Fix score bug"git add .
git commit -m "Update scoring"git add report.py
git commit -m "Add header"