Tecla for GitLab
Tecla reads your GitLab and learns your code from it: your projects, your merge requests, your pipelines and your issues. It finds the reviews, failed pipelines and issues that are yours, and turns each into a task with a plan. For example, when Ana asks you for a review, Tecla adds the task “Review Ana’s merge request for the new export” to your list. You click Run, and Tecla reads the change and prepares its notes for your review.
Free to start. No card needed.
The tasks it finds in GitLab
A review requested from youReview Ana’s merge request for the new export
An issue assigned to youFix the timeout on the reports page
A pipeline that failedFix the failing tests on main
What it learns from GitLab
- Your groups and projects, and the merge requests open in each
- Which pipelines fail often, and what fixed them before
- Which issue each merge request closes, and who approves it
What it does in GitLab
- Finds the cause of a bug and opens a merge request with a test
- Answers review comments and updates the merge request
- Updates the issue when the work ships
Across your apps
A customer reports a broken export in Intercom. Tecla finds the cause in GitLab, opens a merge request and tells the customer when it ships.
How to connect GitLab
In the Mac app, open Connectors, click GitLab and sign in with your own GitLab account.
Questions
- Does Tecla push code or merge on its own?
- No. Each change is a step in the task’s plan, and you see the plan before you start the task. New tasks start by themselves only if you turn on autopilot.
- Which projects can it see?
- The ones your account can see.
Free to start. No card needed.