GitHub
Service domainSOURCE CODE
Arcade Optimized
Arcade.dev LLM tools for Github
43tools
43require secrets
GitHub Toolkit
The GitHub toolkit integrates Arcade with the GitHub API, enabling LLM-powered automation of repositories, pull requests, issues, code review, and project management across personal and organization scopes.
Capabilities
- Repository & file operations: Create branches, read/write/update files (with safe create-vs-overwrite modes), list org and user repositories, retrieve repository metadata, and track activity history.
- Pull requests & code review: Create, update, merge, and inspect PRs; manage reviewers and labels; post and reply to review comments (with diff-aware line targeting); resolve/unresolve conversation threads; check merge readiness; and retrieve review workload and recent activity.
- Issues: Create, update, list, and comment on issues; add issues directly to Projects V2 at creation time; manage labels with fuzzy-matching support.
- Projects V2: List projects across org and user scopes, enumerate project fields and items, search for specific items, and link issues to projects.
- Search & discovery: Full-text code search with inline match context, fuzzy repository search, collaborator discovery with configurable detail levels, and stargazer listing/counting.
- Identity & starring: Retrieve the authenticated user's profile, organizations, and teams; star or unstar repositories.
OAuth
This toolkit uses OAuth 2.0 via the GitHub provider. See the GitHub auth provider docs for setup details.
Secrets
GITHUB_SERVER_URL— The base URL of the GitHub API server. By default this points tohttps://api.github.com. Override this secret when targeting a GitHub Enterprise Server instance (e.g.,https://github.your-company.com/api/v3). Obtain the correct URL from your GitHub Enterprise Server administrator or from your enterprise's GitHub settings. No special permissions are required to determine the URL; it is a configuration value, not a credential.
For guidance on configuring secrets in Arcade, see Tool Secrets. You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.
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.
If the subject_type is not 'file', then the start_line and end_line parameters are required.
If the subject_type is 'file', then the start_line and end_line parameters are ignored.
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). | 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