GitHub
Repositories, issues, pull requests, files, gists, workflows, releases, milestones, projects, search, and 8 webhook triggers
Vendor ID: github · Categories: source-control, productivity
GitHub source-control, project management, and CI extension covering repositories, issues, pull requests, files, gists, workflows, releases, milestones, classic projects, search, and 8 webhook triggers.
Auth
| Credential | Notes |
|---|---|
oauth (GitHub) | The agent will only see repositories your connected user can access on GitHub. Works with a GitHub App whether or not Expire user authorization tokens is enabled, and with a classic OAuth App: with expiry off (the default for an existing app) GitHub issues a non-expiring token and no refresh token, which Scrydon reuses as-is; with expiry on, Scrydon refreshes the token before it expires. |
apiKey (Personal Access Token) | Headless setups. PAT with repo, workflow, and read:org scopes covers the extension's full surface. |
Products
| ID | Name | What it does |
|---|---|---|
github:github | GitHub | The full surface — repos, issues, PRs, files, gists, workflows, releases, milestones, projects, search. |
Editing files from an Agent
Give an Agent File · Edit (exact replacements) (edit-file) rather than File · Update when it changes existing code. Each edit replaces one exact block of text that must occur exactly once in the file. The tool reads and writes the whole file itself, on the branch you name, and commits with the file's current SHA.
This matters because an Agent sees tool results capped at 32 KiB. With File · Update, which replaces the whole file, an Agent that only saw the start of a large file would write back only that part. An edit that doesn't match exactly once is refused and nothing is written.
branch is required. The tool never writes to the default branch by omission.
Scoping a search to one repository
Search · Code, Search · Commits and Search · Issues / PRs search all of GitHub unless you scope them. Set both owner and repo on the tool to keep it in one repository. The tool then adds repo:<owner>/<repo> to every query and drops any repo:, org: or user: qualifier from it, so an Agent can't widen the search. Bound on an Agent's tool, the two fields don't appear in the model's schema at all. Setting only one of them, or a name with spaces or a qualifier in it, is refused rather than searching everywhere.
CLI
Agents can also drive gh directly, additive to the tools above — the whole gh surface, with no hand-written tools. It reads its token from the connected account (no extra setup) and reaches only api.github.com; gh release upload and git-over-HTTPS are out of scope for now and are refused at the network boundary. The harness governs every command at the wire: reads are open, writes need a granted tier, and destructive commands need a person to approve the exact request. See CLI extensions for how this works.
Triggers
Eight webhook triggers covering the most common GitHub events: push, pull_request, issues, issue_comment, release, workflow_run, deployment, and security advisories. See Triggers.