GitHub
Service domainSOURCE CODE
Arcade Optimized
Arcade.dev LLM tools for Github
43tools
43require secrets
GitHub Toolkit
The GitHub toolkit connects Arcade to the GitHub API, enabling LLMs to perform repository management, code review, project tracking, and collaboration workflows on behalf of authenticated users.
Capabilities
- Repository & file operations: Create branches, read and write files (with explicit create-vs-overwrite modes), search code, list repository activities and collaborators, count/list stargazers, and star/un-star repos.
- Issues & pull requests: Create, list, update, and retrieve issues and PRs; manage labels with fuzzy matching; assign users and reviewers; check merge status; merge PRs; and list commits on a PR.
- Code review: Create and list review comments (line-level or file-level), reply to review threads, resolve/unresolve conversation threads, and submit full PR reviews.
- GitHub Projects (V2): List projects across org/user scopes, enumerate project fields and items, search for specific project items, and attach issues to projects on creation.
- User & activity context: Retrieve the authenticated user's profile, orgs, and teams; surface open PRs/issues, recent activity, and the review workload queue.
- Organization & discovery: List org repositories, search repos with fuzzy matching, list repository labels, and enumerate collaborators at configurable detail levels.
OAuth
This toolkit uses OAuth 2.0 with GitHub as the identity provider. See the Arcade GitHub auth provider docs for setup instructions.
Secrets
GITHUB_SERVER_URL— The base URL of the GitHub API server. This is used to target a GitHub Enterprise Server instance instead of the defaulthttps://api.github.com. To obtain the correct value, use your GitHub Enterprise Server hostname in the formathttps://<your-github-enterprise-hostname>(e.g.,https://github.mycompany.com). Your GitHub Enterprise Server admin can confirm the hostname. This secret is not needed when using github.com. For API key–style secrets in Arcade, see how to create tool secrets and manage them at the Arcade dashboard.
Available tools(43)
43 of 43 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Assign a user to a pull request with intelligent search and fuzzy matching. | 1 | ||
Check if a pull request is ready to merge without attempting the merge. | 1 | ||
Count the number of stargazers (stars) for a GitHub repository. | 1 | ||
Create a new branch in a repository. | 1 | ||
Create a new file or overwrite an existing file in a repository.
The explicit mode parameter reduces accidental data loss: the default CREATE mode refuses to
touch existing files, while OVERWRITE must be chosen intentionally. | 1 | ||
Create an issue in a GitHub repository.
Optionally add the created issue to a project by specifying add_to_project_number
and add_to_project_scope. | 1 | ||
Create a comment on an issue in a GitHub repository. | 1 | ||
Create a pull request in a GitHub repository. | 1 | ||
Create a reply to a review comment for a pull request.
Optionally resolve the conversation thread after replying by setting resolve_thread=True
and providing the thread_id (GraphQL Node ID). | 1 | ||
Create a review comment for a pull request in a GitHub repository.
IMPORTANT: Line numbers must be part of the diff (changed lines only).
GitHub's API requires line numbers that exist in the pull request diff, not just any line
in the file. If the line wasn't changed in the PR, the comment will fail with 422 error.
Line comments require start_line and end_line. When subject_type is omitted, providing either
line parameter selects a line comment; otherwise the comment applies to the whole file.
File comments cannot include line-specific parameters.
If the commit_id is not provided, the latest commit SHA from the PR will be used.
TIP: Use subject_type='file' to comment on the entire file if unsure about line positions. | 1 | ||
Get the contents of a file in a repository.
Returns the decoded content (if text) along with metadata like SHA, size, and line count.
For large files, use start_line and end_line to retrieve specific line ranges. | 1 | ||
Get a specific issue from a GitHub repository. | 1 | ||
Get details of a pull request in a GitHub repository. | 1 | ||
Get a repository.
Retrieves detailed information about a repository using the GitHub API. | 1 | ||
Get pull requests awaiting review by the authenticated user.
Returns PRs where user is requested as reviewer and PRs user has recently reviewed. | 1 | ||
Get user's currently open pull requests and issues across all repositories.
Returns open PRs and issues authored by the authenticated user. | 1 | ||
Get the authenticated user's recent pull requests, reviews, issues, and commits.
Returns PRs they authored, merged PRs, PRs they reviewed, issues they opened, and commits pushed | 1 | ||
List issues in a GitHub repository. | 1 | ||
List repositories for the specified organization. | 1 | ||
List fields for a Projects V2 project.
Returns all custom fields configured for the project, including field types
and available options for select/iteration fields. | 1 | ||
List items for a Projects V2 project with optional filtering. | 1 | ||
List Projects V2 across organization or user scopes. | 1 | ||
List commits (from oldest to newest) on a pull request in a GitHub repository. | 1 | ||
List pull requests in a GitHub repository.
By default returns newest pull requests first (direction=DESC).
Organization-wide search returns GitHub's reduced issue-search summary. It preserves the
merged timestamp but does not include repository-list details such as head/base metadata or
detailed mergeability and reviewer data. | 1 | ||
List repository activities.
Retrieves a detailed history of changes to a repository, such as pushes, merges,
force pushes, and branch changes, and associates these changes with commits and users. | 1 |
Page 1 of 2(25 of 43)
Last updated on