Git & GitHub: final assessment

This covers the whole course. Take it after the last module.

Final quiz

1. Where does Git keep a repository's history?
2. What does ?? mean in git status --short?
3. What does git switch -c fix do?
4. Which command undoes a published commit safely?
5. What does git pull do?
6. How is a blob id computed?
7. What is main^2 when main is a merge commit?
8. A file is deleted on one side and modified on the other. What does a merge report?
9. Which commits does git rebase main replay?
10. Your branch is ahead by 1 and behind by 2. What is its state?
11. Which pattern matches release/2.1 in a workflow branch filter?
12. Why must you never rebase commits others have pulled?
13. Why does force-with-lease reject a push that --force would accept?
14. Which merge bases do two branches have after a criss-cross merge?
15. A feat with ! and a fix arrive after v1.4.2. What is the next version?
16. What does git describe print three commits after tag v1.4.0?

Practical assessment: Analyse a repository's history

Without using hints, write a program that reads a repository's commits, branches and tags as text and answers the questions a maintainer asks before a release.

Final project

A mini Git in Python: Write a small version control system in Python that stores real Git objects, so that its ids match git hash-object, and supports the everyday commands.

How it is evaluated

To complete this course