divekit access grant
Give users a role on the repositories of a distribution
divekit access
Give supervisors and testers access to the repositories of a distribution
Synopsis
Give people who are not in the member list access to the repositories of a distribution, and take it away again. Typical cases are a new supervisor who reviews the work, a tutor who helps with it, or a colleague who tests the assignment.
Divekit adds the user to every selected project, in the work and the evaluation repositories alike, and never to a GitLab group. The groups that hold a distribution can also hold other distributions, so a group membership could reveal the work of students outside this one. GitLab notifies the user once per repository.
The commands leave the member list alone. A configured member is refused, because access to every repository would show them the work of all other members; their access belongs to ‘divekit members role’.
Repositories that a later ‘divekit distribute’ creates do not get the user. Running ‘divekit access grant’ again adds them there; it does not change the repositories where the user already has the role.
Usage
divekit access [flags]
Examples
# Let a supervisor read every work and evaluation repository
divekit access grant -d ST2M4 manuel
# Let a tester change one repository
divekit access grant -d ST2M4 maren --access-level maintainer --uuid 123e4567-e89b-12d3-a456-426614174000
# Take the access away again
divekit access revoke -d ST2M4 maren --uuid 123e4567-e89b-12d3-a456-426614174000
Inherited Flags
-l, --loglevel string log level (debug, info, warn, error, fatal) (default "info")
--no-index skip project index update
--non-interactive run in non-interactive mode (fails if interactive input is required)
-y, --yes assume yes/default for all prompts (non-interactive with automatic defaults)