Skip to main content

​
Why integrate Devin with GitLab?

Integrating Devin with your GitLab repositories allows Devin to create merge requests, read and respond to your MR comments, and collaborate effectively with your team. This lets Devin be a true collaborator on your engineering team.
Using a self-hosted GitLab instance? We support GitLab Self-Managed for users on our Enterprise plan. Simply click the dropdown on the “Connect” button and select “Self-Hosted”. See the GitLab Self-Managed Integration guide for full setup instructions.

​
Setting up the Integration

The setup is easy! Here’s how to get started:
  1. Create a new GitLab account specifically for Devin (just like you’d create a personal account). You’ll use this account, not your personal one, during the integration process.
  2. In your Devin account, go to Settings > Connections > Gitlab and click “Connect”.
  3. You’ll be redirected to GitLab where you should:
    • Log in with the GitLab account you created for Devin (not your personal account)
    • Grant the necessary permissions for Devin to work with your repositories
  4. Once completed, you’ll return to the Devin settings page where you can confirm the integration is active.
For GitLab on-premise (self-hosted) installations, the sync of MR status (open, merged, closed) to Devin sessions only happens once a day. This can lead to a temporarily misrepresented MR status in your session or session list until the next sync occurs.

​
Webhook Configuration

Configuring a webhook allows Devin to automatically receive real-time notifications when specific events occur in GitLab (such as opening or updating merge requests and commenting on merge requests). To configure the webhook:
  1. In your Devin account, go to Settings > Connections
  2. Locate the GitLab instance you want to configure
  3. Click the Manage dropdown
  4. Select Configure Webhook
  5. Follow the provided commands to complete the setup