GitHub

GitHub is where your team's code, branches, and pull requests live. Connecting it to X4RGE is the foundation for cloud agents and automations — agents clone your repos, open PRs, and react to events like failed CI or new pull requests.

GitHub is fully supported today — connect end to end from Dashboard → Integrations. Other integrations (Slack, Linear) build on top of this; start here before rolling agents to your team.

What this page is for

You want to…	This page tells you…
Understand why GitHub matters	What agents can and cannot do without it
Connect your org or account	Step-by-step from the dashboard
Know what gets enabled	Runs, PRs, automations, repo picker
Fix common issues	Missing repos, connection errors, PR blocked

Primary integration

Repository-scoped cloud runs and GitHub-triggered automations require this connection. Slack and Linear add notifications and planning on top — they do not replace GitHub for code.

Why connect GitHub

Without GitHub	With GitHub connected
No cloud runs on your code	Agents clone repos and open PRs
Manual copy-paste for reviews	Automations on PR and CI events
Repos missing in Agents workspace	Branches and repos appear in the picker
No "fix CI" workflows	Agents read check status and respond

Without GitHub, agents cannot work on your codebase in the cloud. Most teams connect in the first week of rollout — before cloud agent setup and automations.

How GitHub fits your workflow

X4RGE does not replace GitHub — it works inside your existing repo workflow:

In GitHub	With X4RGE connected
Repositories and branches	Agents clone and branch for cloud runs
Pull requests and review	Agents open and update PRs from runs
CI checks	Automations react when checks fail
Your team's normal git flow	Same flow — agents contribute via PRs

You keep: branch protection, code review, merge rules in GitHub.

X4RGE adds: agent runs, automations, and the repo picker in the Agents workspace.

In practice

Use this table to pick your next step after reading Connect GitHub.

You want to…	Do this
Connect your org's repos	Connect GitHub from the dashboard
Start a cloud run on a repo	Cloud agent setup → pick repo in Agents workspace
Review PRs automatically	Automations with pull request triggers
Fix failing CI	Automation on check / PR events
Add repos later	GitHub app settings — expand access without reinstalling
Repo not in picker	See When something goes wrong

Connect GitHub

Your organization admin or anyone with Integrations access can complete this flow. If your org requires approval, an admin must allow the connection in Settings first.

Open Integrations
In the dashboard, go to Integrations and choose GitHub.
Install the X4RGE GitHub app
Install on your GitHub organization or personal account. GitHub may ask an org owner to approve the app on company accounts.
Grant repository access
Choose all repositories or a selected set. Start with one or two pilot repos, then expand as teams onboard.
Confirm connection
The Integrations page shows connected when installation completes. Repositories sync automatically so they appear in the Agents workspace picker.

Start minimal

Grant access to a pilot repo first. Verify a smoke cloud run and one automation before opening every repository in the org.

What it enables

Once connected, GitHub becomes the source of truth for code in X4RGE. Everything below depends on the repos you granted access to.

Capability	Used for
Clone and branch	Cloud agent runs on your code
Open and update pull requests	Cloud agents and automations ship changes via PR
Read CI / check status	"Fix failing CI" and review workflows
Webhook events	Automations when PRs open, checks fail, or code is pushed
Repo and branch listing	Agents workspace repository picker

Common automation triggers

When GitHub sends…	You might…
Pull request opened or updated	Run an automated review or summary
CI check failed	Start a fix run or notify the team
Comment or mention	Trigger a scoped agent task
Push to main	Post-merge docs or hygiene tasks
App access changed	Refresh which repos X4RGE can see

See Automations for templates and examples.

Permissions

The X4RGE GitHub app requests only what agents need to clone, commit, open PRs, and read CI status. You choose which repositories grant those permissions — not your whole account by default unless you select all repos.

Permission	Why
Repository contents (read/write)	Clone, commit, and push branches
Pull requests (read/write)	Open and update PRs from runs
Checks (read)	See CI results for automations
Metadata (read)	List repositories and branches

Note

Grant access to repositories you actually use. You can add more repos later from GitHub's app settings — no need to reinstall X4RGE.

Admin checklist

Before rolling cloud agents to a team, confirm these items — most are one-time setup:

GitHub app installed on the correct GitHub org or account
Repository allowlist matches teams using cloud agents
Branch protection allows bot PRs (or requires human review — your choice)
Cloud agent setup completed for pilot repos
Secrets for private dependencies configured in cloud environment (not in chat)
Usage and Model control aligned with rollout

When something goes wrong

Most GitHub issues are repo access or sync timing — not a broken connection. Try these before opening a support ticket.

Symptom	What to try
Repos missing in picker	Confirm the repo is selected in GitHub app settings; wait a minute for sync; refresh Integrations
Connection shows error	Re-open Integrations; confirm admin approved the integration if required
Automations not firing	Check the repo is connected and automation scope matches the repository
PR blocked by branch rules	Adjust branch protection or use a bot-friendly workflow in GitHub

For sign-in, Slack, Linear, or deeper sync issues, see Troubleshooting.

Cloud agent setup

Environment and secrets after GitHub is connected.

Automations

GitHub trigger examples and templates.

Agents workspace

Pick a repo and start a cloud run.

Troubleshooting

Integrations, sign-in, and network fixes.