GitHub
GITHUB · DEVELOPER
Repos, issues, and pull requests under that developer’s own access.
Connect GitHub with Fabriq Developer
Your user consents at GitHub. The credential lands in a vault your agent cannot read, and the tool list it gets back is the intersection of that user’s grant and the agent’s own scopes.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting GitHub in practice
There is no read-only scope for private code on an OAuth App: an agent that needs one private repository asks for repo, which is read and write across every public and private repository the user can reach, and GitHub documents that OAuth Apps require organization approval and cannot be approved per repository. The secondary limits bite well before the 5,000 requests per hour primary limit, because 100 concurrent requests and 900 points per minute are easy to cross while paginating.
Scopes that draw scrutiny
repoFull access to public and private repositories including code and webhooks. There is no private-read-only variant, so least privilege is not available on an OAuth App.admin:org"Fully manage the organization and its teams, projects, and memberships".workflowAdds and updates files under .github/workflows, so an agent holding it can change what CI executes.delete_repoDeletes any repository the user administers.admin:repo_hookRead, write, ping and delete access to repository webhooks, which is enough to redirect or silence event delivery.read:audit_logReads the organization audit log.
Rate limits
- 5,000 requests per hour for a personal access token, a GitHub App installation token, or an OAuth App; 15,000 per hour on GitHub Enterprise Cloud.
- Scaled GitHub App installations rise with repository and user count, up to 12,500 requests per hour.
- 60 requests per hour unauthenticated.
- GITHUB_TOKEN inside Actions is 1,000 requests per hour per repository, 15,000 on Enterprise Cloud.
- Secondary limits: no more than 100 concurrent requests, 900 points per minute across REST endpoints, 90 seconds of CPU time per 60 seconds of real time, and 80 content-generating requests per minute with 500 per hour.
- Git LFS: 300 requests per minute unauthenticated, 3,000 authenticated.
Who has to approve
GitHub documents that OAuth Apps require organization approval by default and cannot be approved on a per-repository basis. GitHub Apps differ: repository admins may install them on their own repositories until an org owner turns off "Allow repository admins to install GitHub Apps for their repositories", after which each install becomes a request to an org owner. Org owners can also disable app access requests entirely.
Worth knowing
- A GitHub App installation access token expires after one hour, so the agent needs the app JWT and a mint step in the request path rather than one stored credential.
- Secondary rate limits fire independently of the hourly quota, so a fan-out that respects 5,000 per hour can still be blocked by the 100-concurrent and 900-points-per-minute rules.
- Because the installation limit scales with repository and user count, capacity planning cannot assume a flat 5,000 per hour across tenants.
- GitHub asks for extra justification on the app’s homepage for the Administration permission and for the repository Workflows permission, so those two slow the listing review.
Checked against Scopes for OAuth apps (2026-09-29), Choosing permissions for a GitHub App (2026-09-29), REST API rate limits (2026-09-29), Authenticating as an installation (2026-09-29), Limiting app access requests (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put GitHub behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.