Skip to main content
DEVELOPER LIFECYCLE

​
An agent that lives inside your repo.

Triage the backlog. Comment on the PR. Dispatch an Actions workflow. Draft the release notes. One OAuth connection wires 33 verified GitHub tools into every agent you trust with it — no webhook receiver to host, no dashboard to watch.

Capabilities

​
33 tools across the full developer lifecycle.

GitHub tools cover eight service areas. An agent can read the repo, triage issues, review code, trigger CI, and manage releases — all in one conversation.

33verified GitHub tools
8service areas covered
1OAuth connection needed
0webhook receivers to host

Files and repositories

Read file contents, list repositories for a user or org, retrieve a repo’s license, and pull traffic analytics (popular paths and referrers). Use these to give an agent full context before it drafts a PR comment or creates an issue.
Create, edit, comment on, and lock issues; fetch all open issues by repo or by user. The issue tools are the fastest path to automated triage: point an agent at your inbox and have it label, prioritize, and respond — unattended.
List open pull requests, create code reviews, retrieve and update review sets. Wire a trigger on PR-opened to fire an agent that checks for missing tests, leaves a first-pass comment, and requests reviewers.
Create, update, delete, and list releases. A scheduled agent can pull all merged PRs since the last release, group them by label, and publish a formatted release note — no manual write-up required.
List, enable, disable, get usage, and dispatch workflow runs. An agent can trigger a staging deploy, check its status, and post the result to Slack — all from a single chat message.
Get user repositories, retrieve issues assigned to a user, and invite members to an organization. Use org tools in onboarding automations that set up repo access when a new teammate joins.
Combine github:* tools (GitHub REST API) with the bundled git-official MCP (local Git) for a coding agent that can stage commits and file the PR in a single run. The two are separate — git-official operates on local repos; github:* calls the remote GitHub API.
Setup

​
Connect GitHub.

OAuth is the recommended path — your credentials never touch the desktop, and one connection covers every agent you authorize. A Personal Access Token stored in the Credentials Vault is the alternative for narrower, read-only access.

1

Open the Apps catalog

In the Actionist sidebar click Apps. Search for “GitHub” or browse the Code & Source Control category filter to find the GitHub card.
2

Click Connect GitHub

Open the GitHub detail page and click Connect GitHub. Actionist creates a one-shot OAuth handoff URL and opens your system browser to GitHub’s consent screen.
3

Authorize the OAuth app

GitHub requests four scopes: repo, admin:repo_hook, read:user, and user:email. Authorize the app — GitHub redirects to the Actionist backend callback.
4

Wait for confirmation

Actionist polls the backend every 2 seconds. When the handshake completes, the connection card updates with your connected account name and email. The session window is 10 minutes — if it expires, click Connect GitHub again.
Apps — Actionist
GitHubRepositories, issues, pull requests & webhooks.
OAuth
PAT alternative. Store a Personal Access Token in Settings → Credentials Vault (provider: github, display name e.g. "GitHub PAT — work"). Any MCP or skill that declares env:GITHUB_TOKEN picks it up automatically — one entry covers every tool that needs it.
Agents

​
Give an agent access to GitHub tools.

Enable via the Tools tab

Open any agent in the Agents studio → Tools tab. GitHub tools (github:issues:create, github:repositories:getIssues, and the rest) appear there once the connection is established — toggle the ones this agent needs.

Example task

“Summarize open issues in actionist/catalog-test, group by label, and post the digest to #engineering on Slack.” The agent calls github:repositories:getIssues, processes the result, then posts via the Slack connection — one prompt, two integrations.
In practice

​
Three automations teams run on day one.

Real workflows built from the 33 GitHub tools above. Each fires automatically — no manual steps after the initial setup.

Sam · Solo founder
When a PR is opened, the agent reads the diff with github:pullRequests:listFiles, checks for missing tests, posts a structured first-pass review comment, and requests reviewers via github:pullRequests:createReview — all before a human has looked at it.
saves ~25 min per PR
Omar · Agency owner
Every night at 02:00, a scheduled agent calls github:repositories:getIssues across 6 client repos, groups open issues by label and age, and posts a consolidated digest to Slack #dev-ops — 6 repos checked, one message.
saves ~3 hrs/wk
Dario · Sales
When a new issue lands, the agent reads the title and body, matches it against the label taxonomy via github:issues:listLabels, applies bug, priority:high, or area:* tags with github:issues:update, and posts a triage acknowledgment — 47 issues triaged in the first week, zero manual labels.
live in 10 min
Triggers

​
Fire an agent on any GitHub event.

GitHub is an App Trigger source. When a push lands, a PR opens, or an issue is created, the connected agent wakes up immediately — no polling, no hosted receiver. Pick an event below to see the pipeline in action.

pull_request: openedissues: openedpush: refs/heads/main
Actionist receives the webhook payload and wakes the assigned agent.
Reads context, calls the right GitHub tools, acts on the result.
First-pass review comment + reviewer request filed on the PR.Issue labeled, prioritized, and acknowledged with a triage comment.Deploy summary posted to Slack #engineering and release draft updated.
agent · pr-reviewer · trigger: pull_request opened
00:00Received PR #142: feat/add-webhook-retry
tool · github:pullRequests:listFiles · #142
00:0112 files changed — no test file for src/retry.ts
tool · github:pullRequests:createReview · #142
00:02Review posted. Requested @team/backend as reviewers.
agent · issue-triage · trigger: issues opened
00:00New issue #89: “Search returns 500 on empty query”
tool · github:issues:listLabels
00:01Classified: bug · priority:high · area:search
tool · github:issues:update · add labels
00:02Labels applied. Triage comment posted.
agent · release-bot · trigger: push to main
00:00Push landed — 3 commits since last release tag
tool · github:releases:list
00:01Last release: v2.14.0 · 3 merged PRs since
tool · github:releases:create · draft: v2.15.0
00:02Draft created. Slack #engineering notified.
No polling. The App Trigger subscribes to the GitHub webhook — your agent wakes the instant the event fires, not on the next polling interval.
No hosted receiver. Actionist manages the callback URL and HMAC signature verification. You paste one URL into GitHub’s Webhooks settings — done.
Any event, any repo. Choose from push, PR opened/merged/closed, issue opened/labeled, release published, and more. One trigger per event type per agent.
1

Open Reactions

Navigate to the agent that should respond → Reactions tab → New Trigger.
2

Select App Trigger

Choose App Trigger as the source type (subtitle: “GitHub · GitLab · installed apps”). Pick GitHub from the app selector and choose the event type.
3

Configure the webhook

A setup panel provides a callback URL and a one-time secret. Paste both into GitHub’s Webhooks settings page for your repository or organization.
The webhook setup secret is shown once. Copy it to GitHub’s Webhooks settings page immediately — it cannot be retrieved after you close the panel.
For full details on trigger types, filter rules, and agent routing, see the Reactions page.
Best practices

​
Tips before you go live.

PAT vs OAuth — when to use each

OAuth grants full private repo access (repo scope) and is the right choice for org-wide agents. A scoped PAT stored in Credentials Vault is safer when an agent should only read public repos or a narrow subset of a private org. Store the PAT under provider: github and it routes automatically to every tool that needs it — no per-tool token entry.
GitHub occasionally omits the x-oauth-scopes header even when the token was minted from the requested scopes. Actionist handles this automatically by falling back to the originally requested scopes for capability projection. If GitHub tools appear missing after a reconnect, disconnect and reconnect once more via the Apps detail page.
Issues, PRs, and releases default to per_page: 50. For repos with heavy activity, include a state filter (state: open) or a date range in the agent’s task description. This prevents large, token-expensive payloads that slow down responses.
Multiple MCPs that declare provider: github all route to the same stored credential automatically. Enter the token once in Credentials Vault and every tool — git-official, github-official, and any skill that needs env:GITHUB_TOKEN — is covered.
The bundled git-official MCP operates on local Git repositories (clone, commit, push, branch operations). The github:* tools call the GitHub REST API remotely (issues, PRs, releases, Actions). Use both together for a coding agent that can stage local changes and then file a PR against the remote repo.
One connection

​
Ship faster with an agent in your repo.

Connect GitHub once. Assign the tools your agent needs. Let it triage, review, and release — while you focus on building.

Open the DashboardSet up a trigger

33 verified GitHub tools · One OAuth connection · No webhook receiver to host.
App Triggers fire instantly on push, PR, and issue events.

Keep going

​
Related topics.

Credentials Vault

Store and rotate GitHub PATs in the encrypted vault — one entry flows to every tool that needs it.

Reactions

Set up App Triggers to fire agents on push, PR-opened, and issue-created events.
https://cdn.simpleicons.org/slack

Slack

Route GitHub event summaries into Slack channels or DMs — the most common pairing.
https://cdn.simpleicons.org/linear

Linear

Bridge GitHub issues to Linear tickets for cross-tool project tracking.