Skip to main content
Connect GitLab to Tembo to open merge requests to improve your codebase.

​
Features

  • Scan for TODO comments in your codebase
  • Scan for security issues
  • Scan for performance issues
  • Scan for technical debt
  • Scan for refactoring opportunities
  • Automatically fix failed CI/CD pipelines
  • Respond to MR comments and review feedback

​
Installation

1

Install

Navigate to the Integrations page in Tembo and click the Install button next to GitLab.
2

Authorize

Authorize Tembo to access your GitLab account. You can select specific repositories or all repositories. You’ll be redirected back to the Integrations page when complete.
3

Activate Repositories

After syncing completes (may take a few minutes), select which repositories you want Tembo to scan under “Active Repositories” on the Integrations page.Only repositories you activate here will be scanned for issues and receive improvement merge requests.Tip: If repositories don’t appear after a few minutes, use the sync button on the Integrations page to manually trigger a refresh.

​
Managing Your Integration

​
Manual Sync

If you’ve added new repositories to your GitLab account or modified repository permissions, you can manually sync to refresh the list:
  1. Navigate to the Integrations page
  2. Find the GitLab integration card
  3. Click the sync button (circular arrow icon)
  4. Wait for the sync to complete - the button will show a loading indicator while syncing
The sync process will discover any new repositories you’ve granted access to and update existing repository metadata.

​
Supported Webhooks

Tembo listens to the following GitLab events and maps them to automation triggers (reference them as gitlab.<event> in your triggerName, e.g., gitlab.merge_request.opened). Tembo subscribes only to the events listed here (not every GitLab webhook). The Integrations page in the app shows the live set enabled for your org. If you need an additional event, contact [email protected].
  • merge_request.opened
  • merge_request.updated
  • merge_request.closed
  • merge_request.merged
  • note.created (for comments on merge requests)
See Automations for how to create triggers that start automations from these events.

​
Usage

​
Automated Scanning

Once activated, Tembo automatically scans for TODO comments, security issues, performance problems, technical debt, and code quality issues.

​
Merge Requests

When Tembo finds an addressable issue, it creates a merge request with the proposed fix, detailed description, and assigns it for team review.

​
Working with Merge Requests

​
Reviewing Merge Requests

Review Tembo’s MRs just like any other team member’s work:
  • Examine the changes and verify they align with your requirements
  • Leave comments directly on the code if you need changes
  • Use the Feedback Loop feature to have Tembo address your review comments automatically

​
Commenting on MRs

When reviewing Tembo’s merge requests, you can request changes or improvements by tagging @tembo in your comments. This ensures Tembo responds to your specific feedback while ignoring internal team discussions or comments directed at other team members. Example: 
@tembo Please update this function to include error handling
Without the @tembo tag, Tembo will not respond to the comment, allowing for cleaner team communication.

​
Failed Pipeline Detection

Tembo automatically monitors your GitLab CI/CD pipelines and detects when they fail. When a pipeline fails due to broken tests, linting errors, or other issues, Tembo will analyze the failure, identify the root cause, and create an MR with a fix. This helps maintain a healthy CI/CD pipeline without manual intervention.

​
Troubleshooting

  • Repositories not appearing? Wait 2-5 minutes for initial sync, verify permissions were granted during installation, try the manual sync button, and check group access permissions if applicable.
  • @tembo mentions ignored? Use exact format @tembo (case-sensitive), verify the repository is activated, and ensure note.created webhook is enabled on the Integrations page.
  • MRs not being created? Confirm the repository is activated, check that Tembo has branch creation permissions, and verify no duplicate MRs already exist for the issue.

​
Best Practices

  • Configure repository settings to match your team’s preferences
  • Use Rule Files to help Tembo understand your coding standards
  • Set up Hooks to customize Tembo’s behavior for your workflow