GitHub API
Arcade Unoptimized
Tools that enable LLMs to interact directly with the GitHub API.
818tools
818require secrets
Arcade Toolkit enables seamless interaction between LLMs and the GitHub API, allowing for efficient management and development of GitHub repositories. It provides developers with tools for automation, collaboration, and project management.
Capabilities
- Automate GitHub actions and workflows for repositories.
- Manage branches, access permissions, and team collaborations.
- Handle repository secrets, issues, pull requests, and releases.
- Perform analytics on contributions, notifications, and security alerts.
- Integrate GitHub Apps and customize environment settings.
OAuth
Provider: Github
Scopes: None
Secrets
The toolkit supports several types of secrets such as GitHub tokens, webhooks, and environment variables. For example, it allows the management of GIT_SERVER_URL securely.
Available tools(818)
818 of 818 tools
| Tool name | Description | Secrets | |
|---|---|---|---|
Accept a GitHub repository invitation.
This tool accepts an invitation to join a GitHub repository for the authenticated user. Use it when you need to confirm participation in a repo after receiving an invitation. | 1 | ||
Grant specified apps push access to a protected branch.
Use this tool to grant specific GitHub Apps push access to protected branches in repositories. Apps must have 'write' access to 'contents' to be authorized.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Add custom labels to a self-hosted runner in an enterprise.
Use this tool to attach custom labels to a self-hosted runner within an enterprise on GitHub. Requires authentication with a token that has the `manage_runners:enterprise` scope. | 1 | ||
Add a new email to the authenticated GitHub user's account.
Use this tool to add an email address to the authenticated GitHub account of the user. This action requires user scope authentication.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 1 | ||
Add an authorized SSH key to GitHub Enterprise.
This tool adds an authorized SSH key to a GitHub Enterprise account. It is useful when you want to securely access your GitHub repositories using SSH. Make sure to provide the SSH key in the required format. | 1 | ||
Add a reaction to a GitHub release.
Use this tool to create a reaction to a specific release on GitHub. If a reaction already exists, it will return a confirmation with status 200 OK. | 1 | ||
Add a GPG key to your authenticated GitHub account.
This tool allows you to add a GPG key to your GitHub account after authenticating via Basic Auth or OAuth with the appropriate scope. Use it to enhance security by managing GPG keys on GitHub. | 1 | ||
Add labels to a GitHub issue to categorize it.
Use this tool to apply one or more labels to a specific issue in a GitHub repository. It helps in categorizing and organizing issues for better project management.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Add custom labels to a self-hosted runner in an organization.
This tool adds custom labels to a self-hosted GitHub Actions runner configured in an organization. Use this tool when you need to organize or categorize runners with specific labels. Requires authentication with an access token having the `admin:org` scope. | 1 | ||
Add organization access to a self-hosted runner group in an enterprise.
Use this tool to add an organization to a selected list that can access a self-hosted runner group. The runner group's visibility must be set to 'selected'. Requires an access token with 'manage_runners:enterprise' scope. | 1 | ||
Add or update a collaborator on a GitHub repository.
Use this tool to add a new collaborator or update the permission level of an existing collaborator on a GitHub repository. The invitee will receive a notification, and changes are instantly applied. Be aware of rate limits and permissions restrictions. | 1 | ||
Add or update a GitHub team's permissions on an organization project.
Use this tool to add a project to a GitHub team or update a team's permissions on a project within the same organization. The user must have admin permissions for the project. | 1 | ||
Add a collaborator to an organization project.
This tool adds a collaborator to a specified organization project and assigns a permission level. It requires the user to be an organization owner or a project admin. | 1 | ||
Add a reaction to a GitHub commit comment.
Use this tool to add a reaction (like, love, etc.) to a comment on a GitHub commit. It confirms if the reaction was already added with an HTTP `200` status. | 1 | ||
Add a reaction to a GitHub issue comment.
Use this tool to add a specific reaction to a comment on a GitHub issue. It checks if the reaction type has already been added, returning an HTTP `200` status in that case. | 1 | ||
Add a reaction to a GitHub issue.
Use this tool to add a specific reaction to a GitHub issue. If a reaction has already been added by the user, a response with HTTP status 200 will confirm this. Suitable for managing issue reactions on GitHub repositories. | 1 | ||
Add a reaction to a GitHub team discussion.
Use this tool to add a specific reaction emoji to a team discussion in a GitHub organization. It requires OAuth access tokens with the `write:discussion` scope. This is useful for engaging with team discussions directly through the API. | 1 | ||
Adds a reaction to a pull request review comment on GitHub.
Use this tool to add a reaction to a specific pull request review comment on GitHub. This can be helpful for acknowledging comments or expressing opinions quickly. A successful addition results in an HTTP `200` status. | 1 | ||
Add a reaction to a GitHub team discussion comment.
Use this tool to add a reaction emoji to a specific GitHub team discussion comment within an organization. Useful for engaging with team discussions or acknowledging comments. Requires appropriate OAuth scope. | 1 | ||
Add repository access to a self-hosted runner group.
This tool is used to add a repository to the list of selected repositories that can access a self-hosted runner group within an organization. It should be called when you need to manage repository access for a self-hosted runner group with `selected` visibility. Requires authentication with an `admin:org` scoped access token. | 1 | ||
Add a repository to a GitHub installation for the authenticated user.
Use this tool to add a specific repository to a GitHub installation. The authenticated user must have admin access to the repository. A personal access token is required to authenticate the user. | 1 | ||
Add a repository to a GitHub organization secret.
Use this tool to add a repository to an organization's secret in GitHub when the `visibility` is set to `selected`. Requires an access token with `admin:org` scope or a GitHub App with `dependabot_secrets` permission. | 1 | ||
Add a repository to an organization's secret.
This tool adds a specified repository to an organization secret with 'selected' visibility. It requires authentication with an access token having 'admin:org' scope. GitHub Apps need 'secrets' organization permission. | 1 | ||
Add a repository to an organization's selected variables.
Use this tool to add a repository to a specific organization variable that is available to selected repositories on GitHub. This requires an access token with `admin:org` scope or GitHub App permission `organization_actions_variables:write`. The repository and organization must have the `visibility` field set to `selected`. | 1 | ||
Adds a repository to a GitHub required workflow.
Use this tool to add a repository to a GitHub required workflow. Ensure the workflow is set to run on selected repositories. Authentication with an access token having `admin:org` scope is required. | 1 |
Page 1 of 33(25 of 818)
Last updated on