Connect wtih GitLab

Our integration with Gitlab allows you to sync repositories to Venue.sh as entities.

Note: Prerequisites

An organization in Venue.sh
A role of Owner or above
A GitLab account with an appropriate permission level

Creating a Personal Access Token Gitlab

Tip:

As a best practice, we recommended setting up a dedicated service account for this token.

Note:

GitLab's documentation on creating personal access tokens describes the process in detail. While we endeavour to keep this document current, GitLabs's process may have changed.

Go to https://gitlab.com or your hosted instance of GitLab and sign in.
Click your profile pic, then select preferences → Access Tokens → Add new token.
Give the token a name and define its expiration period.
Tip:
Remember, when the token expires, you will need to replace it to ensure no lapse in functionality.
Choose the following scopes/permissions for the token:
- api
- read_repository
- write_repository
Click Create personal access token.
Copy the token as it cannot be retrieved once you leave the page.

Creating an OAuth app

To fully integrate Gitlab with Venue.sh, you must set up an OAuth app.

Go to https://gitlab.com or your hosted instance of GitLab and sign in.
Click your profile pic, then select Preferences → Applications → Add new application
Insert the following properties:
- Name: Venue.sh
- Redirect URI: https://organization.venue.sh/api/auth/gitlab/handler/frame
Tip:
Your organizations redirect URI can be found in app when adding a Gitlab connection on the right sidebar.
Choose the following scopes/permissions for the application:
- Confidential
- read_user
- read_repository
- write_repository
- openid
- profile
- email
Click Save application.
Note the Application ID and Secret values.
Click Continue.