GitHub

1. What you get with GitHub
2. How the integration works
3. Good to know

GitHub is where most of the world's code lives — over 100 million developers and the default home for open source and private team repositories alike. If your sites live in GitHub repos, deployment should start there too. Connect GitHub to Rocketeers and every push to your chosen branch becomes a deployment, automatically.

#What you get with GitHub

• Push-to-deploy: merge to your production branch and the site ships itself.
• Full support for private repositories and organisation-owned repos.
• Deploy from any branch, so staging can track develop while production tracks main.
• Your existing workflow stays intact — pull requests, reviews and branch protection all work exactly as before.
• No deployment scripts to write or maintain.

#How the integration works

Connecting is an OAuth flow: authorise Rocketeers with your GitHub account, pick the repository for each site and choose the branch to deploy from. Rocketeers registers a webhook on the repository, so GitHub notifies it the moment you push. Each push to the watched branch triggers a fresh deployment of your site; pushes to other branches are ignored. Repository access can be limited to just the repos you select, and revoking the integration from your GitHub settings severs access instantly.

#Good to know

• Works with personal accounts and organisations; organisation repos may need an owner to approve the connection, depending on your org's settings.
• You choose which repositories Rocketeers can see — it never needs blanket access to your account.
• Deployments trigger on push, which includes merged pull requests — a natural fit for PR-based workflows.
• A free GitHub plan is all you need; private repositories are included on GitHub's free tier.