Product
Auto-fix pull requests
For the failures it understands, Tessel writes the fix and a test, then opens a pull request in your repository for your team to review.
How it works
Once an incident has a cause, Tessel checks whether it is one it can fix safely. Renamed columns, changed types, new values in an accepted-values test, a broken ref after a refactor and an incremental filter that skips late rows are all common, well understood and boring to fix by hand.
For those, Tessel writes the change on a new branch, adds or updates a test that would have caught the failure, and opens a pull request on GitHub. The description explains what broke, why, and what the change does, with a link to the incident. Your CI runs as usual.
Tessel never merges anything and never writes to your warehouse. If it isn’t confident, it explains the cause and leaves the fix to you.
Step by step
-
Decide
Tessel checks the cause against more than 40 fix patterns and your repository’s conventions.
-
Write
It edits the model or YAML on a new branch and adds a test that fails before the fix and passes after.
-
Review
A pull request opens with the reason and the incident link. Your CI runs; your team merges.
By the numbers
- of failures fixed without a human writing code
- 83%
- Team plan customers, last 90 days
- median time to a proposed fix
- 11 min
- From run failure to open pull request
- of fix pull requests merged unchanged
- 79%
- The rest are edited, then merged or closed
The pull requests read like a colleague wrote them: what broke, why, and a test that proves the fix. We merge about four in five as they are.
Questions about auto-fix pull requests
Will Tessel ever merge on its own?
No. It opens pull requests and nothing more. Branch protection, required reviews and CI all apply exactly as they do for your team.
Which repositories does it support?
GitHub, including GitHub Enterprise Server 3.9 and later. Tessel only needs access to the repositories that hold your dbt project or pipeline code.
Can we limit what it fixes?
Yes. Turn fix patterns on or off per project, limit pull requests to certain folders, or switch to explain-only mode for a repository.
See it on your own pipelines
A 30-minute demo on a copy of your project, or start free with up to 25 models.