Add minor remarks in Git exercise (#194)

Author: uekerman

01_version_control/git_exercise.md

@@ -4,8 +4,8 @@ Deadline: **Wednesday, October 30, 2024, 9:00**
 
 ## Preparation
 
-- Work on the exercises in groups of two. One of you creates a new organization on GitHub (free plan) and adds their partner.
-- Import the [exercise repository](https://github.com/Simulation-Software-Engineering/git-exercise) and name it `git-exercise` again. We refer to this repository as the *upstream* repository.
+- Work on the exercises in groups of two. One of you creates a new organization on GitHub (public, free plan) and adds their partner.
+- Import the [exercise repository](https://github.com/Simulation-Software-Engineering/git-exercise) and name it `git-exercise` again. Make it public to get access to all features we need. We refer to this repository as the *upstream* repository.
 - Add a branch protection rule for the `main` branch of the repository:
     - Require a pull request before merging
     - Require linear history
@@ -15,7 +15,7 @@ Deadline: **Wednesday, October 30, 2024, 9:00**
 
 - There are three separate exercises. Each one consists of an individual Python file `exerciseX.py`. The exercises build upon each other, work from one to three. Each exercise is described in the comments at the top of the respective Python file.
 - Each exercise has two tasks: A and B. Distribute the two tasks and **work on them in parallel**.
-- For each task, create a new branch with an appropriate name (e.g., `ex-1-task-A`) and use appropriate commit messages (not `Solve task A`).
+- For each task, create a new branch with an appropriate name (e.g., `ex-1-task-A`) and use appropriate commit messages (not `Solve task A`, but `Fix missing copy in Vector construction` or similar).
 - When ready, push the new branch via `git push -u <remote> <branchname>` to your own remote and open a pull request to the `main` branch upstream (i.e. use the feature branch workflow, but with feature branches on forks).
 - Assign your partner as reviewer. Review, fix problems, and eventually merge. For the best learning experience, use a different order of steps in every exercise.
 - **Goal of the exercises**: Create a linear history with readable commit messages.