CI and GitHub Actions
Keep GitHub. Your checks run next to the agents.
Checks are the automatic tests that run on every change. PatchWell runs them where the agents work, so an agent can see a failure and fix it in the same thread. Your code, your pull requests and your GitHub Actions stay on GitHub.
Add a coupon field to checkout
-
pipeline test
failed checkout total: expected $45.00, got $44.99
-
claude
The new test caught a rounding error in the discount. I fixed it and ran the checks again.
-
pipeline test
passed reported to GitHub
Your workflow file, in PatchWell
| GitHub Actions | PatchWell |
|---|---|
runs-on: ubuntu-latest | runner: linux-2 |
needs: [build] | needs: [build] |
services: postgres | services: postgres |
strategy.matrix | matrix |
actions/cache | cache |
${{ secrets.API_KEY }} | $API_KEY |
uses: actions/checkout | already checked out |
Most settings keep their names. Our pipeline guide lists the rest, one row each.
-
fix loop
The agent fixes what it broke
A failed check shows up in the thread. The agent reads the log, fixes the code and runs the checks again, so nobody copies errors from one screen to another.
-
github
GitHub keeps working
Your GitHub Actions keep running. PatchWell can wait for them before a change goes in, and it can post its own results to GitHub, so your branch rules still apply.
-
moving over
Run both until you’re sure
Copy one workflow over and run it in both places. When PatchWell’s results match, you can switch that workflow off on GitHub, or keep it.
-
fresh machines
A clean machine for every job
Each job gets its own machine, used once and then thrown away. If the machine breaks under a job, PatchWell starts a new one and tries again.