https://divekit.org/docs/2-divekit-cli/access/Recent content in divekit access on DivekitHugoenhttps://divekit.org/docs/2-divekit-cli/access/grant/Mon, 01 Jan 0001 00:00:00 +0000https://divekit.org/docs/2-divekit-cli/access/grant/<!-- Code generated by cmd/docgen. DO NOT EDIT. --> <h2 id="synopsis">Synopsis</h2> <p>Give one or more GitLab users a role on the repositories of a distribution.</p> <p>By default the users get the reporter role on every work and evaluation repository. Reporter can read and clone a repository but not push to it. Choose another role with &ndash;access-level and narrow the repositories with &ndash;target and &ndash;uuid. A user who already is a direct member of a repository gets the new role there, also when it is lower than before.</p>https://divekit.org/docs/2-divekit-cli/access/revoke/Mon, 01 Jan 0001 00:00:00 +0000https://divekit.org/docs/2-divekit-cli/access/revoke/<!-- Code generated by cmd/docgen. DO NOT EDIT. --> <h2 id="synopsis">Synopsis</h2> <p>Remove the direct membership of one or more GitLab users from the repositories of a distribution.</p> <p>Without &ndash;target and &ndash;uuid every work and evaluation repository is affected. A repository the user is no member of stays unchanged, so the command can be repeated safely.</p> <p>A user can also reach a repository through a membership of a parent group, for example when someone added them to the group in GitLab. Divekit never changes groups, so it checks every repository after the removal and names the ones the user can still reach, together with the role the group grants. Remove that membership in GitLab.</p>