GitHub
Work on issues and pull requests in GitHub. Agents search and triage issues, read discussions, comment, open issues, read pull requests and their diffs, review code and read files in a repository.
- Category
- Developer & IT
- Ways to connect
- 2
- Actions for agents
- 12
- Triggers
- 3
Ways to connect
A company admin connects GitHub from the Integrations page in Everdeck. Keys, tokens and secrets are encrypted before they're stored, and the connection's Test button checks it works before any agent uses it.
-
Fine-grained personal access token API key
Copy a key or token from GitHub and paste it into Everdeck.
-
Your GitHub App (acts as the user who connects it) Your OAuth app
Create an OAuth app of your own with GitHub, paste its client ID and secret into Everdeck, then sign in to GitHub and approve access. Access runs through your own app, never one Everdeck shares with other customers.
What agents can do with GitHub
An agent can only use the actions its charter grants. Each action has a risk tier, and the tier decides whether it runs on its own, asks first or always asks a person.
Runs on its own 9
Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.
-
List repositories Tier 0 · Read Outside content
List the repositories this connection can reach, most recently pushed first, with owner, name, visibility, default branch and open issue count (which includes pull requests). Use owner and name in the other actions.
-
Search issues and pull requests Tier 0 · Read Outside content
Search issues and pull requests across repositories with GitHub search syntax. Always include is:issue or is:pr, for example "repo:acme/web is:issue is:open label:bug", "org:acme is:pr is:open review-requested:@me" or "repo:acme/web is:issue checkout error in:title". Add repo: or org: to stay inside your own repositories; without them GitHub searches every public repository. Returns at most 1,000 results and is limited to 30 searches a minute; to page through one repository's issues use list_issues.
-
List issues in a repository Tier 0 · Read Outside content
List a repository's issues, most recently updated first. Pull requests are included and carry a pull_request field. Filter by state, labels, assignee or changes since a time.
-
Read an issue Tier 0 · Read Outside content
Read one issue (or a pull request's conversation) by number: title, body (Markdown), state and reason, labels, assignees, milestone, issue type, author and comment count. Use list_comments for the discussion.
-
Read comments Tier 0 · Read Outside content
Read the comments on an issue or on a pull request's conversation, oldest first. Inline code review comments are not included.
-
Triage an issue Tier 2 · Reversible Outside content
Close or reopen an issue (or pull request) and change its labels, assignees, milestone or type. Send only what changes; labels and assignees replace the current lists, so read the issue first and send the full list. Subscribers are notified.
-
Read a pull request Tier 0 · Read Outside content
Read one pull request: title, description, state, draft, whether it is merged or mergeable, source and target branches, head commit, requested reviewers, labels and size (commits, changed files, additions, deletions). Use list_pull_request_files for the diff.
-
Read a pull request's changes Tier 0 · Read Outside content
List the files a pull request changes with their status, line counts and patch (unified diff). The patch is left out for binary or very large files. At most 3,000 files.
-
Read a file Tier 0 · Read Outside content
Read a text file from a repository at a branch, tag or commit (the default branch when ref is left out), or list a directory. Long files are cut to about 10,000 characters (truncated: true); binary files, and files larger than Everdeck reads (8 MB), return only their size.
Asks first 3
Anything a customer or the public sees. By default a charter grants these as Ask first: the agent sends an approval request and waits for a yes. A company admin can switch one to Auto in the charter after confirming with their second factor. Even then, once an agent has read outside content, such as a customer's email, its tier 3 and 4 actions need a person by default for the rest of that session.
-
Open an issue Tier 3 · External Outside content
Open an issue in a repository. Watchers are notified, and on a public repository everyone can see it. Labels, assignees, milestone and type are silently ignored unless the account has push (write) access to the repository.
-
Comment on an issue or pull request Tier 3 · External
Add a Markdown comment to an issue or to a pull request's conversation. Subscribers are notified, and on a public repository everyone can read it.
-
Review a pull request Tier 3 · External
Submit a code review on a pull request: a summary comment or a request for changes, with optional comments on specific lines. Approving is deliberately not offered so a person always gives approvals. The author and subscribers are notified; on a public repository everyone can read it.
Actions marked Outside content return what people outside your company may have written, such as emails or comments. Agents treat it as information to check, never as instructions.
What can start work
Set a trigger up on the Intake page, and your rules there turn what arrives into tasks for your agents.
-
An issue was opened, edited, closed, reopened, labeled, assigned or transferred (webhook event issues).
GitHub sends it to the address the Intake page gives you, as it happens.
-
Someone commented on an issue or on a pull request's conversation (webhook event issue_comment, action created).
GitHub sends it to the address the Intake page gives you, as it happens.
-
A pull request was opened, got new commits, was marked ready for review, had a review requested or submitted, or was closed or merged (webhook events pull_request and pull_request_review).
GitHub sends it to the address the Intake page gives you, as it happens.
Work an agent can take on
Examples for apps in Developer & IT. What an agent does with GitHub depends on the actions you grant it.
- Sum up new errors or incidents and point out the ones that need a person first.
- Read the latest deployment or build logs when something breaks.
- Comment on issues with what it found.
Set it up
The GitHub setup guide walks through each way to connect: what to set up first and the fields to fill in, then how to start work from its triggers on the Intake page.
GitHub is a separate service with its own terms. Everdeck isn't affiliated with or endorsed by it.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.