Shipping automatically: connecting a GitHub repository

Uploading a ZIP is the fastest way to get a first version of a site live. But once a project is real — once you're pushing changes regularly — doing that by hand for every change gets old fast.

Connecting a GitHub repository removes that step entirely. Once it's linked, every push to your chosen branch triggers a build and a publish on its own. You keep writing code and committing like normal; the live site just stays in sync.

You still get the same deployment history and status visibility as a manual publish — the only thing that changes is who clicks "deploy." After it's wired up, the answer is: nobody has to.

If something in a push breaks the build, you'll see it reflected in the deployment status rather than discovering it by visiting the site — which tends to catch problems a lot earlier.