SMPH department IT directors and their designees have can be delegated the capability to create GitLab sub-groups for teams in their departments and designate a group owner. You or that group owner can invite, remove, and manage the members and create projects (repositories) within that sub-group.  

Step-by-step guides

Create a department-level group

Information needed:

• SMPH department
• Group visibility: public (visible to unauthenticated users), internal (visible to all authenticated users), private (visible to specific, named users)
• Group owner(s) (e.g., the IT director and any additional designees)

Steps:

1. Navigate to https://git.doit.wisc.edu/smph or https://git.doit.wisc.edu/smph-public.
2. Click on "New subgroup" then "Create group".
3. Set department name and abbreviation.
4. Set appropriate visibility (e.g., generally "public" if it is in SMPH (Public) and internal or private if on in SMPH).
5. Unless otherwise specified, select "Software Developer", "My company", and click Create group
6. Navigate to Subgroup Information > Members and invite the appropriate owners. (Note that members from higher level groups will be inherited.)

Email template

To: <department IT director>
Subject: GitLab Department-level Group

Hello,
SMPH IT has created a GitLab group for your department. You may now create sub-groups for teams in your department that need them and designate a group owner. You or that group owner can invite, remove, and manage the members and create projects (repositories) within that sub-group.  

Create a team/group/center/initiative-level subgroup

Information needed:

• SMPH department
• Team/group/center/initiative subgroup name
• Group visibility: public (visible to unauthenticated users), internal (visible to all authenticated users), private (visible to specific, named users)
• Group owner(s)

Steps:

1. Consider routing request to the owner of the appropriate IT director. They can create projects within their subgroup.
2. Navigate to the appropriate department within https://git.doit.wisc.edu/smph or https://git.doit.wisc.edu/smph-public.
3. If the department subgroup does not yet exist, see Create a department-level subgroup above.
4. Click on "New subgroup" then "Create group".
5. Set appropriate visibility (e.g., generally "public" if it is in SMPH (Public) and internal or private if on in SMPH).
6. Unless otherwise specified, select "Software Developer", "My company", and click Create group
7. Navigate to Subgroup Information > Members and invite the appropriate owners and/or other members. (Note that members from higher level groups will be inherited.)

Managing group membership

Information needed:

• Subgroup 
• Member emails and roles
  • Guests have limited visibility into groups.
  • Developers can create projects in groups. (This can be restricted.) 
  • Owners can manage members and create/delete subgroups.

1. Navigate to the appropriate subgroup within https://git.doit.wisc.edu/smph or https://git.doit.wisc.edu/smph-public.
2. Click on Subgroup Information > Members and invite the member(s) with the appropriate role. (Note that members from higher level groups will be inherited.)

Managing project team membership

Information needed:

• Project 
• Member emails and roles
  • Guests can view code and pages, and create comments and issues.
  • Developers can view analytics, run CI/CD pipelines, move issues, create and approve merge requests, create/edit milestones and releases, create branches, push to unprotected branches.
  • Maintainers can manage team members, edit web hooks and project settings, push to protected branches, manage push rules.
  • Owners can rename, transfer, or delete projects.

1. Navigate to the appropriate project under https://git.doit.wisc.edu/explore.
2. Navigate to Project Information > Members and invite the member(s) with the appropriate role. (Note that members from higher level groups will be inherited.)

Create a project

Information needed:

• SMPH department
• Team/group/center/initiative subgroup for the project
• Project name
• Project "slug" (i.e., the short version of the name that is used in URLs)
• Project visibility: public (visible to unauthenticated users), internal (visible to all authenticated users), private (visible to specific, named users)
• Project owner(s)
  • The owner can later add other team members.
  • Optionally, they could have you add other owners, maintainers, developers, and/or guests by name or by group.
• Is the project being imported from another Git repository or GitLab instance?
  • Importing from another Git repository can be done via URL.
  • Importing from another GitLab instance can be done via GitLab export/import.
  • See DoIT GitLab Resources for Migrating to git.doit.wisc.edu

Steps:

1. Consider routing request to the owner of the appropriate team/group/center/initiative subgroup. They can create projects within their subgroup.
2. Navigate to the appropriate team/group/center/initiative subgroup in https://git.doit.wisc.edu/smph or https://git.doit.wisc.edu/smph-public.
3. If the team/group/center/initiative subgroup does not yet exist, see Create a team/group/center/initiative-level subgroup above.
4. Click on "New project"
5. Select blank or template for project, fill the subsequent form with the information you gathered, and click Create Project
6. Navigate to Project Information > Members and invite the appropriate owners. (Note that members from higher level groups will be inherited.)

Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.