Tecla for GitHub
Tecla reads your GitHub and learns your work from it: your repositories, what’s being built, who reviews what and what broke. It finds the notifications that need you and turns each one into a task with a plan. For example, when Ana asks you for a review, Tecla adds the task “Review Ana’s pull 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 GitHub
A review requested from you
Review Ana’s pull request for the new export
A comment on your pull request
Answer Leo’s question about the cache change
A build that failed
Fix the failing tests on main
What it learns from GitHub
- Your repositories and what’s being built in each
- Who reviews what, and who owns which part of the code
- What shipped, what broke and how it was fixed
What it does in GitHub
- Finds the cause of a bug in the code and opens a pull request with a test
- Answers review comments and updates the pull request
- Links the work to its issue, and updates it when it ships
Across your apps
Northwind’s support lead emails about a broken export. Tecla finds the cause in the repository, opens a pull request with a test, updates the Linear issue and replies to the email.
Use cases with GitHub
Work that starts or ends in GitHub and crosses your other apps, step by step.
How to connect GitHub
In the Mac app, open Connectors and sign in to GitHub as you usually do. Nothing to install.
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 repositories can it see?
- The ones your account can see.
Free to start. No card needed.