Ploy × GitHub

Ploy provisions the repo for you — git clone your site repo into your local workflow and drive updates with your favorite tools, all versioned, reviewable, and revertable.

What you can do

Six ways teams put GitHub to work with Ploy.

  • A dedicated repo, provisioned for you.

    Ploy sets up a GitHub repo in its own org and commits every site change there as real, reviewable code.

  • Version-control every page.

    Each edit Ploy ships is a commit — full history, full diff, one-click revert within the app when you need it.

  • Bring your own Agent and Tokens.

    After the initial Ploy setup, your repo is seeded with an AGENTS.md that instructs your favorate agent harness to collaborate on the repo. Bring your tools, bring your tokens.

  • Keep your code review workflow.

    Mirror the repo to your own GitHub org, where you can apply your policies to your site edits so your team keeps the guardrails it needs. Sync back to the Ploy remote to prepare a release.

  • Keep one source of truth.

    Designers, marketers, and engineers all work against the same repo — engineers pull it locally, edit, and git push to sync changes back into Ploy, so there’s no shadow copy of the site.

  • Turn release notes into pages.

    Ploy reads merged changelog entries and drafts the customer-facing version of each.

How it connects

Three steps. Then GitHub works inside Ploy.

01

Connect GitHub in Workspace Settings.

In Workspace Settings → Ploy Code Sync, connect your GitHub account on behalf of your team, then invite teammates to the repo.

02

Read and write, two-way sync.

Every site change Ploy ships is committed to the repo, and every commit you push back is pulled into Ploy — changes flow both ways, always in sync.

03

Watch Ploy work.

Ploy sees the repo context on every edit it makes, every report it runs — no extra setup, it's already in the agent context.

GitHub pairs well with these.

Connect GitHub and ship today.

Slurp your existing site in 60 seconds, plug in GitHub, and watch Ploy start using it on the next page it builds.