GitHub Integration
GitHub Integration
Section titled “GitHub Integration”GitHub integration lets your Content and Coding agents commit changes, create pull requests, and trigger deployments.
Setup Options
Section titled “Setup Options”Deploy Key (Recommended)
Section titled “Deploy Key (Recommended)”Scoped to a single repository. Most secure for production.
- Generate an SSH key pair for your agent
- Add the public key as a deploy key on your repo (Settings > Deploy Keys)
- Enable “Allow write access”
- Configure the agent with the private key path
Personal Access Token
Section titled “Personal Access Token”Broader access across repositories. Simpler setup.
- Go to GitHub Settings > Developer Settings > Personal Access Tokens
- Create a fine-grained token with:
- Repository access: select specific repos
- Permissions: Contents (read/write), Pull Requests (read/write)
- Add the token to your agent’s configuration
GitHub CLI (gh)
Section titled “GitHub CLI (gh)”If gh is already authenticated on your agent’s host:
gh auth statusThe agent can use gh commands directly. No additional setup needed.
What Agents Can Do
Section titled “What Agents Can Do”| Action | Agent | Command |
|---|---|---|
| Commit + push | Content | git commit && git push |
| Create PR | Content | gh pr create |
| Check CI status | QA | gh run list |
| View PR comments | Support | gh pr view |
| Merge PR | Content (with approval) | gh pr merge |
Auto-Deploy Integration
Section titled “Auto-Deploy Integration”When your Content Agent pushes to a repo connected to Vercel, Netlify, or Cloudflare Pages, the deployment happens automatically. The QA Agent can then verify the deployment by checking the live URL.
Content Agent → pushes commit → Vercel deploys → QA Agent verifiesNo additional configuration needed if your repo already has CI/CD set up.