Update Git slides and exercise for WT26/27

Author: MakisH

01_version_control/git_exercise.md

@@ -9,24 +9,25 @@ Deadline: **Wednesday, October 28, 2026, 9:00**
 - Add a branch protection rule for the `main` branch of the repository:
     - Require a pull request before merging
     - Require linear history
-- Finally, everybody forks the repository into their own namespace.
+- Finally, both of you should fork the repository into your own namespace.
 
 ## Idea of the Exercise
 
 - 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`, 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.
+- 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 any 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.
 
 ## Pytest and Python
 
 - In each task, you typically need to make one of already existing tests pass. We use `pytest` here (you will learn more about `pytest` after Christmas):
-    - Install from [PyPI](https://pypi.org/project/pytest/): `pip install --user pytest`.
+    - Make a Python virtual environment: `python -m venv venv` and activate it: `source venv/bin/activate`.
+    - Install `pytest` from [PyPI](https://pypi.org/project/pytest/): `pip install pytest`.
     - Run all tests of a file with `python3 -m pytest exerciseX.py`.
-    - Run a specific test with `python3 -m pytest exerciseX.py -k TESTNAME`.
-- Ask if you are stuck with Python issues (quick search on Google often helps as well). This exercise is about Git, not Python.
+    - Run a specific test with `python3 -m pytest exerciseX.py -k TESTNAME` (e.g., `-k test_vector_index_access`).
+- Ask if you are stuck with Python issues! This exercise is about Git, not Python.
 
 ## Submission
 

01_version_control/merge_rebase_slides.md

@@ -100,7 +100,6 @@ slideOptions:
     ```
 
 - A merge takes all commits from `feature` to `main`.
-- Sorted by timestamp
 - Graph view: `git log --graph`
 
 ---
@@ -153,7 +152,8 @@ We use here:
     - Create a merge commit
     - Squash and merge
     - Rebase and merge
-- Look at a PR together, e.g. [PR 2346 from preCICE](https://github.com/precice/precice/pull/2346) (will be closed eventually)
+
+<!-- - Look at a PR together, e.g. [PR 2346 from preCICE](https://github.com/precice/precice/pull/2346) (will be closed eventually) -->
 
 > What do the options do?
 

01_version_control/standards_slides.md

@@ -46,7 +46,7 @@ slideOptions:
 
 ---
 
-## Special Files
+## Special Files (1)
 
 Certain files lead to special formatting (normally directly at root of repo):
 
@@ -55,18 +55,37 @@ Certain files lead to special formatting (normally directly at root of repo):
     - ... gets rendered on landing page (and in every folder).
 - `LICENSE`
     - ... contains software license.
-    - ... gets rendered on right sidebar, when clicking on license, and on repo preview.
+    - ... gets rendered on the sidebar and on repo preview.
+
+---
+
+## Special Files (2)
+
 - `CONTRIBUTING.md`
     - ... contains guidelines for contributing.
     - First-time contributors see banner.
 - `CODE_OF_CONDUCT.md`
     - ... contains code of conduct.
-    - ... gets rendered on right sidebar.
+    - ... gets rendered on the sidebar.
+
+---
+
+## Special Files (3)
+
+- `CITATION.cff`
+  - ... contains preferred citation details.
+  - ... gets rendered on the sidebar.
+  - ... export to BibTeX.
+- `AGENTS.md`
+  - ... contains context and instructions for GenAI.
+  - ... more and more coding agents read it.
+
 
 ---
 
 ## Issues and PRs
 
-- Templates for description in `.github` folder
+- Templates for description are placed in the `.github` folder.
 - `closes #34` (or several other keywords: `fixes`, `resolves`) in commit message or PR description will close issue 34 when merged.
-- `help wanted` label gets rendered on repo preview (e.g. *"3 issues need help"*).
+- `co-authored-by: name <email>` will attach multiple authors.
+- `help wanted` issue label gets rendered on repository preview<br/> (e.g. *"3 issues need help"*).

01_version_control/workflow_slides.md

@@ -108,6 +108,7 @@ slideOptions:
     - Easier to review
     - Faster to merge --> fewer conflicts
     - Easier to squash
+- Since 2026, GitHub also allows [stacked PRs](https://docs.github.com/en/pull-requests/how-tos/stacked-pull-requests)
 
 ---