GitHub Actions
Watchfire merges the branch. Actions runs your tests on it as normal.
What is GitHub Actions?
GitHub Actions and Watchfire run on opposite sides of the merge. Watchfire is local — it produces the branch and the merge. Actions is your existing CI, running on the resulting commits.
GitHub Actions + Watchfire
When Watchfire merges a task's branch into your default branch, the push triggers your existing GitHub Actions workflows exactly as it would for a hand-pushed commit. There's no Watchfire-specific runner, no extra step, no hosted execution layer in the middle.
That separation is deliberate. The Watchfire daemon's job stops at the merged branch — running tests, building releases, deploying to staging, anything beyond that is your CI pipeline doing what it's already configured to do.
If a Watchfire-produced commit fails CI, treat it exactly like any other broken commit on the default branch: revert, fix, push. Watchfire doesn't need to be involved in the rollback.
Get started with Watchfire
Install in seconds. Define tasks. Let agents ship code for you.
Download for macOSAvailable for macOS, Linux, and Windows
# Install via Homebrew (macOS)brew tap watchfire-io/tapbrew install --cask watchfire-io/tap/watchfire# Set up your project and gowatchfire initwatchfire task add "Build the login page"watchfire start --allIncludes GUI, CLI, and daemon. Also available via Homebrew.