My idea for next semester's GitHub repository structure


(Deb Deppeler) #1

For next semester, I am imagining one repo with folder hierarchy as follows:

cs400-deppeler-201809
admin-teachers-only (not visible to public or students)
program-1
solution
grading
write-up-pages

program-5
solution
grading
write-up-pages
students (visible to current-students only if possible)
program 1
starter-source-code-and-data
student-team-1 (team 1’s work and is visible to student-team1 only if possible)
student-team-2

student-team-150
program 2
starter-source-code-and-data
student-team-1
student-team-2

student-team-150

My Questions

  1. Should the student “folders” be folders, branches, forks, what?
  2. Can students in current semester see work in admin and from repositories from past semesters?
  3. Can I “lock” repositories after a due date.

Thanks for any tips before I give student submissions via GitHub classroom a try,

-Deb