Skip to Content
ResourcesIntegrationsDeveloper ToolsGitHub

GitHub

Service domainSOURCE CODE
GitHub icon
Arcade Optimized

Arcade.dev LLM tools for Github

Author:Arcade
Version:6.0.5
Auth:User authorization via the Github auth provider
43tools
43require secrets

GitHub Toolkit

Arcade's GitHub toolkit connects LLMs to the GitHub API, enabling agents to manage repositories, code, pull requests, issues, projects, and user activity on behalf of authenticated users.

Capabilities

  • Repository & file operations: Create and switch branches, read file contents with line-range support, create or overwrite files with explicit mode control, update specific line blocks, search code across the authorized scope, list and inspect repositories (personal, org, collaborators, activity history), and manage stars.
  • Pull requests & reviews: Create, update, merge, and inspect PRs; list commits and review comments; create review comments (diff-line-aware) and file-level comments; reply to threads; submit, resolve, and unresolve review threads; check merge readiness; manage reviewers and labels with fuzzy matching.
  • Issues & labels: Create, update, and retrieve issues; add comments; manage labels (add/remove, fuzzy-matched) on issues and PRs; list all repository labels.
  • GitHub Projects V2: List projects (org or user scope), list and filter project items, search for specific items, list project fields (including select/iteration options), and attach issues to projects at creation time.
  • User & team context: Identify the authenticated user with org and team membership (WhoAmI), retrieve open PRs and issues authored by the user, surface review workload (awaiting and recently completed), and fetch recent activity across PRs, reviews, issues, and commits.
  • Search & discovery: Fuzzy-search accessible repositories, list org repositories, list and enrich collaborators (basic / org-members / full-profile tiers), and count or list stargazers.

OAuth

This toolkit uses OAuth 2.0 via GitHub. See the Arcade GitHub auth provider docs for setup details.

Secrets

  • GITHUB_SERVER_URL — The base URL of the GitHub API server. For standard GitHub.com usage this is not needed, but it is required when targeting a GitHub Enterprise Server instance. Set it to the root URL of your enterprise instance (e.g., https://github.example.com). Obtain this from your GitHub Enterprise Server administrator or your instance's hostname. See GitHub Enterprise Server docs for context.

Secrets are configured via the Arcade secrets guide and can be managed at https://api.arcade.dev/dashboard/auth/secrets.

Available tools(43)

43 of 43 tools
Operations
Behavior
Tool nameDescriptionSecrets
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