Integrations

One GitHub App. Every builder that syncs to a repository.

BulkAudits does not plug into a builder directly. It reads the live site, and it writes through GitHub: a pull request on the repository your builder syncs, which you merge and the builder pulls back. That keeps every change reviewable and keeps the builder in charge of its own files.

GitHub App

Installed per repository with contents, pull request and checks permissions. It opens a branch, commits typed transforms, opens the pull request with the finding and its evidence in the body, and listens for pushes so a watcher can re-check the live site. It never pushes to your default branch.

Connect a repository

Builders

  • Lovable

    Lovable keeps a two-way sync with a GitHub repository it creates for the project.

    After the merge: Merge the pull request on GitHub and Lovable pulls the change into the project; the next prompt builds on the fixed code.

    What breaks on Lovable sites

  • Bolt

    Bolt can push a project to a GitHub repository and keep it updated from the editor.

    After the merge: Merge on GitHub, then pull the repository back into Bolt (or re-import) so the editor and the live site match.

    What breaks on Bolt sites

  • v0

    v0 projects deploy through Vercel; the code lives in a GitHub repository connected to that Vercel project.

    After the merge: Merge on GitHub and Vercel deploys the fix; later v0 changes that touch the same files show up as ordinary diffs.

    What breaks on v0 sites

  • Base44

    Base44 syncs the project code with a GitHub repository through its main branch.

    After the merge: Merge on GitHub; Base44 picks the change up from main, and you publish from the builder as usual.

    What breaks on Base44 sites

  • Replit

    Replit has Git built in; connect the Repl to a GitHub repository and push from the Git pane.

    After the merge: Merge on GitHub, pull in the Git pane, and redeploy the Repl so the live site carries the fix.

    What breaks on Replit sites

Hosting

Vercel
Merging the pull request triggers a production deploy of the repository branch Vercel tracks. The watcher re-checks the live site ninety seconds after the push lands.
Netlify
Same flow: the merge is a push to the tracked branch and Netlify builds it. Netlify sites that serve an SPA shell need prerendering for the Receipt layer; the chapter on server-visible content covers it.
Builder hosting
Lovable, Bolt, Base44 and Replit host the site themselves and pull merged changes back into the project; each builder guide says how the round trip works and what to publish afterwards.

Builder and host names identify the products a site is built or served with. BulkAudits is not affiliated with or endorsed by any of them.