GitHub

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

GitHub is where most teams already keep their code, review changes and discuss work. Connecting it to Rocketeers turns that repository into the source of truth for your servers: pick a repository and branch for a site, and every push becomes a deployment, with no build scripts or webhooks to wire up by hand.

#What you get with GitHub

• Your repositories listed in Rocketeers, so linking a site to its code takes a couple of clicks.
• Push to deploy: Rocketeers registers a webhook and deploys the chosen branch whenever new commits land.
• Deploy keys added for you, so servers can pull code without sharing personal credentials.
• AI agent pull requests: coding agents in Rocketeers work on a branch and open a pull request for your team to review.
• Personal and organisation repositories alike, wherever your token has access.

#How the integration works

Create a personal access token in your GitHub developer settings with access to the repositories you want to deploy, then add it to Rocketeers. Rocketeers uses the GitHub API to list repositories and branches, install the deploy key and webhook when you connect a site, and create branches and pull requests when an agent finishes a task. Nothing is merged without you: pull requests wait for review like any other.

#Good to know

• A fine grained token limited to specific repositories keeps access tight. You can revoke it in GitHub at any moment.
• Rocketeers never creates GitHub accounts or changes your billing. Your plan and limits stay exactly as they are.