Tebby Code
Bugs in. Reviewed pull requests out.
Tebby Code turns reproduced bugs in your FiveM scripts into staff-approved pull requests, ready for your team to review and merge.
The bug report and the fix are days apart.
A player reports a broken script, it sits in a ticket, and eventually someone with repo access finds an hour to reproduce it. Most small server teams have exactly one person who can do that work. Tebby Code closes the gap: it reproduces the issue against your connected repository and opens a pull request your team reviews like any other.
How Tebby Code works.
It reproduces before it writes
Tebby works from a real, reproduced failure rather than a guess at what the report meant, so the fix addresses the actual bug.
It opens a pull request
The change arrives as a normal PR on your connected GitHub repository, with the reasoning and the diff laid out for review.
Your team merges, or doesn't
Nothing reaches your server without a human merging it. Tebby has no path to production that skips your review.
Questions we get asked.
- Do you store my source code?
- No. Your source code is never stored. Tebby Code reads what it needs to produce a change and keeps only the proposed diff and pull-request metadata such as number, URL, and branch. The Tebby Code Policy sets this out in full.
- Can Tebby push straight to my server?
- No. Every change is a pull request that a human on your team has to review and merge. There is no unsupervised path from Tebby to production, by design.
- Which languages and frameworks does it handle?
- It is built for FiveM server work, which in practice means Lua scripts and the resource structure around them, working against the products your store actually sells.
- What do I need to connect?
- A GitHub repository, via the Tebstack GitHub App. You choose which repositories are visible, and you can disconnect at any time.
- Which plan includes it?
- Tebby Code is available from the Pro plan at $19.99 per month. Max adds priority in the Tebby Code queue for teams shipping fixes continuously.
Ship fixes without waiting on one person.
Connect a repository, hand Tebby a real bug report, and review the pull request that comes back.