Bring Fiddle to your app
Deployments
Tell Fiddle where each branch runs, so the toolbar shows up there and comments land on the right branch.
A deployment is a branch running in an environment: pricing on Preview, main on QA, main on Production. Each new build brings it up to date.
The toolbar only loads where your app is known to run: deployments GitHub reports, your allowed domains, and localhost.
Connect GitHub (recommended)
On the app's page, press Connect GitHub and pick the repository. Vercel, Netlify, Cloudflare Pages and most CI report deployments to GitHub, so each preview is listed the moment it's live, with its branch, environment, commit and pull request.
GitHub Actions jobs with an environment and url report theirs too. With the app installed, a pull request also gets a comment linking its stories.
Allowed domains
For hosts GitHub doesn't hear about, add a domain in App settings, optionally with its environment (qa.acme.com → QA).
- Use
*for the part a host makes up:acme-git-*-team.vercel.app. *never stands for the whole domain.*.vercel.appisn't allowed.
Other ways in
- A webhook of your own: the URL and secret from App settings, content type
application/json, events Deployment statuses and Pull requests. - A deploy script:
add_deploymentover MCP, or Add a deployment in a branch's menu. - Your dev server: nothing to set up. With
data-branchon the tag, the toolbar works on localhost.
Environments
Preview, QA, Production. A deployment takes its environment from its allowed domain, else from GitHub. A page can act as another with data-environment="QA". Each comment records where it was left and where it was resolved.
Production
Put the tag in production with data-launcher="hidden". Visitors load nothing past the small script. Your team opens the toolbar with the shortcut ⌥ ⇧ F, ?fiddle in the URL, or your own Feedback button calling Fiddle.open().