Connect GitLab
Deploy from gitlab.com or a self-managed GitLab: pick projects from the repository list, clone private ones, deploy on push and preview merge requests.
Under Settings → Team → Git providers, add a GitLab connection with your GitLab address (gitlab.com or your own instance) and an access token. Create the token in GitLab → Preferences → Access tokens, or use a group access token, with the api scope. Railyard stores it encrypted and uses it only to list projects, clone and add webhooks.
What you get
- Your GitLab projects appear in the repository picker next to GitHub, on New app and on the canvas.
- Private projects clone with the connection’s token; the app keeps a plain repository URL.
- New apps get their push webhook added for you, so a push to the tracked branch deploys.
- Merge requests get a preview environment when previews are on for the app, torn down when the MR is merged or closed. Merge requests from forks never get previews, because a preview carries the app’s variables.
Disconnecting keeps every app’s repository URL, but private projects stop cloning and pushes stop deploying until you connect again.
Bitbucket has push and pull-request webhooks only: paste the webhook URL from the app’s Settings → Auto-deploy into the repository.