I’m teaching a course for the second time this fall using materials developed in GitHub last spring and stored in a GitHub organization. Since the course materials already exist and are in public GitHub repositories, I’m wondering what people do to manage them and avoid confusing the students with too many visible repositories for future lessons, exercises, etc.
My question is what do you do with the course materials when re-teaching a class? Do you…
- Hide the future lessons/exercises by making the repositories private?
- Keep all past course materials publicly available to the class even though they may change prior to their use in class?
- Use branches for different years/semesters?
- Do something smarter that I’ve not yet thought of?
What about old student repositories generated using GitHub classroom? Do you…
- Keep all student repositories, since they will possibly be used in the future by the students?
- Ask students to fork their repositories and delete the old private copies in your organisation?
- Just delete the repositories with reckless abandon?
- Use a better solution?
Any feedback would be welcome. I’m sure this will touch on some philosophical GitHub issues, and I should say I don’t have any bias. I just want a solution that allows me to keep the existing materials easily accessible for my use/modification and minimises student confusion.