The peer review commands (see Peer review (assign-reviews, check-reviews and end-reviews commands)) do not currently support group assignments.
RepoBee supports group assignments such that multiple students are assigned to
the same student repositories. To put students in a group, they need to be
entered on the same line in the students file, separated by spaces. This is the
only way to group students, the
-s option on the command line does not
support groups. As an example, if
slarse should be in one group,
glennol solo, the following students file would work:
glassey slarse glennol
There is no difference in using RepoBee with student groups in the student file. For example, running the setup command from Set up student repositories would then have the following result:
$ repobee setup --mn task-1 task-2 --sf students.txt [INFO] cloning into master repos ... [INFO] cloning into file:///home/slarse/tmp/task-1 [INFO] cloning into file:///home/slarse/tmp/task-2 [INFO] created team glennol [INFO] created team glassey-slarse [INFO] adding members glennol to team glennol [WARNING] user glennol does not exist [INFO] adding members glassey, slarse to team glassey-slarse [INFO] creating student repos ... [INFO] created repobee-demo/glennol-task-1 [INFO] created repobee-demo/glassey-slarse-task-1 [INFO] created repobee-demo/glennol-task-2 [INFO] created repobee-demo/glassey-slarse-task-2 [INFO] pushing files to student repos ... [INFO] pushing, attempt 1/3 [INFO] Pushed files to https://some-enterprise-host/repobee-demo/glassey-slarse-task-2 master [INFO] Pushed files to https://some-enterprise-host/repobee-demo/glassey-slarse-task-1 master [INFO] Pushed files to https://some-enterprise-host/repobee-demo/glennol-task-2 master [INFO] Pushed files to https://some-enterprise-host/repobee-demo/glennol-task-1 master
Note the naming convention for group repos:
<student-1>-<student-2>-[...]-<master-repo-name>. The associated teams
follow the same convention, but without the trailing
And that is all you need to know to start doing group assignments!
The naming scheme has a weakness: it can create fairly long names, and GitHub has a hard limit for repo names at 100 characters. RepoBee will therefore crash (on purpose) if a Team or repo name exceeds 100 characters. There is no workaround for this problem at the moment.