GitLab

1. What you get with GitLab
2. How the integration works
3. Good to know

GitLab bundles source control, reviews and CI in one place, and plenty of teams prefer it for exactly that reason. Rocketeers plugs into your GitLab projects the same way it does with GitHub: link a project and branch to a site, and pushing code is all it takes to ship it.

#What you get with GitLab

• Your projects listed in Rocketeers, including those in groups your token can reach.
• Push to deploy: a webhook on the project tells Rocketeers to deploy the chosen branch on every push.
• Deploy keys added automatically, so servers pull code without anyone's personal credentials.
• AI agent merge requests: coding agents in Rocketeers work on a branch and open a merge request for review.
• Your existing GitLab CI keeps running untouched alongside Rocketeers deployments.

#How the integration works

Create a personal access token in your GitLab user settings with the api scope and add it to Rocketeers. Rocketeers then uses the GitLab API to read projects and branches, register the deploy key and webhook when you connect a site, and create branches and merge requests when an agent completes a task. Every change an agent makes arrives as a merge request, so your team decides what gets merged.

#Good to know

• Give the token an expiry date that suits your policy and rotate it in Rocketeers when it runs out.
• Group and project access levels in GitLab still apply, so the token only sees what its owner can see.
• Your GitLab plan and billing are unaffected. Rocketeers only talks to the API with the token you provide.