Fix a bug straight from the Slack thread where the bug was reported
Point at the thread, and the fix comes back as a pull request with the errors behind the bug.
In the post: zero switching between tools, and no SQL written in six months.
- From Boris Cherny's post
- Runs when someone asks for a fix in a Slack thread
- Freemium
Connect the apps here, then add the workflow. Kavela runs the workflow when you press Run until you clear it to run on its own.
The workflow
Exactly what will run, and the app each step works in. You can change any step before you add the workflow.
When someone asks for a fix in a Slack thread
- Slack
Read the bug thread in Slack.
In Slack
- Sentry
Pull the matching errors and stack traces from Sentry.
In Sentry
- GitHub
Find the cause in the code and write the fix with a test.
In GitHub
- GitHub
Open a pull request and reply in the thread with the link.
In GitHub
Customize
What should the workflow know about you?
How should each step be done?
Which other apps should the workflow use, and how?
Where should results go, and how should each message read?
Take the workflow further
Each app below adds a step. Turn one on to see the step in the workflow above; the app joins the setup.
Linear Freemium
Files the bug as an issue linked to the pull request
Sign in once
BigQuery Free
Answers follow-up questions with your product data
Sign in once
Works well with the Engineering Agents pack, and with any agent already in your workspace.
What to expect
A second agent checks every run against the workflow's checklist before the result reaches you.
- Small slips are fixed first
- A result close to passing is corrected before the check.
- A miss goes back
- A result missing a check goes back with the exact gap and is redone.
- Three tries, then you
- If the result still falls short after three tries, you get the work and what is missing.
Put the workflow to work.
Connect the apps here, then add the workflow. Kavela runs the workflow when you press Run until you clear it to run on its own.