Source code
GitLab
Connect a GitLab.com account so Dave can read code and open merge requests.
Dave can read your code and open merge requests on GitLab.com. Self-managed GitLab instances are not supported.
Connect
Section titled “Connect”-
In Dave, go to Integrations → Add integration → GitLab. A popup opens on GitLab.com.
-
Sign in as the user Dave should act as, and authorize Dave.
Dave sees the projects where that user has at least the Developer role. Archived projects are skipped.
Permissions
Section titled “Permissions”Dave connects over OAuth and asks GitLab for one scope:
apiDave acts as the GitLab user who authorized it, with that user’s access. It needs the Developer role or higher on each project it works in. A project where the user is only a Guest or Reporter does not show up. Any GitLab.com user can connect, and no group owner approval is needed.
To limit what Dave can reach, connect with a dedicated GitLab user that is a member of only the groups and projects Dave should work in.
Manage the connection
Section titled “Manage the connection”The user who authorized Dave can review or revoke it at Authorized applications. Click path is avatar → Edit profile → Applications → Authorized applications.
Disconnect in Dave revokes Dave’s token on GitLab, so Dave no longer appears under Authorized applications. If it is still listed, choose Revoke there.
Revoking Dave on GitLab, or removing the user from a group, cuts off Dave’s access right away. To restore it, Connect again.
Selecting repositories
Section titled “Selecting repositories”After connecting, choose which of those projects Dave should work in. This narrows Dave’s attention; it does not change what the GitLab user can access.
Troubleshooting
Section titled “Troubleshooting”- “GitLab authorization could not be completed.” The popup was closed, or GitLab refused the authorization. Connect again.
- A project is missing. Check that the connecting user has at least the Developer role on it and that it is not archived.