Your flows run on every PR — and the merge waits for them
Demo coming soon
Until now you asked for a demo when you remembered to. Now the demo is part of the merge. Put your flows in .tada/flows/ on the branch, install the GitHub App, and Tada opens every preview deploy — a real browser, the actual deployed build, the flow the PR claims to ship. No Playwright specs to write or maintain.
A passed flow posts its demo on the PR as a status check — watch link, no login, so reviewers can see it working before they approve. A failed flow is a red required check: the merge is blocked, no demo goes out, and what you get is the frame where it broke, and the few before it.
How it fits your pipeline
- Flows ride the PR — flow files live on the branch, so the run always matches the deploy SHA it tests. Change the feature and its flow in the same commit.
- Triggered by the preview deploy — the run starts the moment a running app exists, same as any other check. Nothing to remember, nothing to kick off.
- The whole set replays — every run replays all your flows against the new build, so a PR can't quietly break the flow next door.
- Branch protection does the enforcing — mark the check required and an unverified feature simply can't merge.