GitHub

Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.

This action allows the authenticated user to accept a pending invitation to collaborate on a repository. By providing the unique invitation ID, the user can join the repository seamlessly.

This action adds GitHub Apps to the list of apps allowed to push to a protected branch in an organization repository. The branch must already have protection rules with restrictions enabled. Apps specified must be installed on the repository. Note: This feature is only available for organization-owned repositories.

This action adds a specified user as a collaborator to a given GitHub repository. If the user is already a collaborator, their permissions can be updated accordingly.

Adds one or more GitHub users as assignees to an issue. This action adds to the existing assignees (does not replace them). You need push access to the repository to modify assignees. Use 'remove_assignees_from_an_issue' to remove assignees.

This action allows the authenticated user to add new email addresses to their GitHub account. It handles unverified emails, ensuring that duplicates and verified emails from other accounts are managed correctly.

Tool to add a custom field to a user-owned GitHub Projects V2 project. Use when you need to add fields like status, priority, or custom data to organize project items.

Tool to add an issue or pull request to a user-owned GitHub project. Use when you need to add existing repository items to a project board.

This action allows users to add specified labels to an existing issue in a repository. If the labels do not exist, they will be created automatically.

This action allows you to add custom labels to a self-hosted runner that belongs to a specific organization. It ensures that previously applied labels remain intact and prevents duplicates from being added.

This action allows you to add a GitHub user to a specific team within an organization or update their existing role. If the user is not already a member of the organization, they will receive an invitation to join.

Grants or updates a team's access permissions (read, write, or admin) on a classic organization project. Use this to control which teams can view or modify specific projects within your organization. Note: This only works with classic projects, not GitHub Projects V2.

This action allows you to set or update the permissions of a specific team for a given repository within an organization. It makes managing access levels to repositories easier and helps ensure that teams have the appropriate level of access to perform their tasks.

This action allows you to add a specified GitHub user as a collaborator to an existing organization project. The user will be granted a specific permission level for that project. Note: This is for classic organization projects only.

This action adds a specified repository to a designated GitHub App installation, enabling the app to access that repository. The user must have admin permissions for the repository in question and must also have access to the installation.

This action adds a specified repository to an organization secret within GitHub. It ensures that the repository can access the secret, which is useful for managing sensitive information securely.

This action allows a specified repository to access an organization's Dependabot secret. It ensures that the repository can utilize the secret for necessary operations, enhancing security through limited visibility. Important: This action only works when the secret's visibility is set to 'selected'. If the secret has 'all' or 'private' visibility, the API will return a 409 Conflict error. You must configure the secret's visibility when creating or updating it.

This action allows the addition of custom labels to a self-hosted runner for a specific repository. It enables users to conveniently categorize and manage runners with labels that reflect their statuses or capabilities.

This action allows you to add a specific repository to the access list of an organization's secret. It ensures that your secret remains secure and only shared with selected repositories.

This action allows you to add a specific repository to the access list of a GitHub Actions variable at the organization level. This is useful for managing access to sensitive variables for specific repositories within an organization.

This action allows you to grant a specified repository access to a user-level Codespaces secret. It ensures that the Codespaces created for that repository can securely use the secret for their operations.

This action allows authenticated users to add their social media accounts to their GitHub profile. The provided URLs will be publicly visible on their profile page, enhancing their online presence.

Adds required status check contexts to a protected branch. Use this when you want to require additional CI/CD jobs to pass before merging. The branch must already have branch protection with status checks enabled.

Tool to add a sub-issue to a parent GitHub issue using GraphQL. Use when you need to establish a parent-child relationship between issues. Requires the 'sub_issues' GraphQL feature to be enabled.

Add teams to push access list for a protected branch. This grants specified teams the ability to push to the branch while keeping existing team permissions. Only works for organization repositories with branch protection restrictions enabled.

This action adds specified users to the list of people who can push to a protected branch. It only works on organization repositories where branch protection with restrictions is already configured. Users must have write access to the repository.

This action adds specific organization members to the list of users who can use Codespaces billed to the organization. The users must already be members of the organization. Note: The organization's Codespaces access must be configured to 'selected_members' mode before using this action.

This action retrieves a map of all top-level GitHub REST API resource URLs and their templates. It allows clients to easily discover the available functionalities provided by the API.

Approves a workflow run that originates from a pull request in a forked repository. This action requires manual approval when the run is subject to specific workflow rules.

This action assigns a specified organization role to a designated team within a GitHub organization. It requires the organization name, team slug, and role ID to perform the assignment.

This action assigns a specified role to a given user within a specified organization on GitHub. It validates the provided role ID and ensures the user is either a member or collaborator before the assignment occurs.

Lists Docker packages for the authenticated user that had namespace conflicts during the Docker-to-GHCR migration. Note: This endpoint is deprecated as the Docker registry migration period ended Feb 24, 2025. May return a deprecation notice instead of package data.

This action allows you to block a specified GitHub user by their username. Once blocked, the user will no longer be able to interact with your account or repositories.

This action allows an organization admin to block a specified user from the organization. Once blocked, the user will no longer be able to contribute, collaborate, or fork any of the organization's repositories. This operation is idempotent - blocking an already blocked user will succeed.

This action cancels a GitHub Pages deployment that is either in progress or queued. It requires the owner, repository name, and the unique deployment ID to identify the specific deployment to cancel.

Tool to cancel an active GitHub sponsorship using GraphQL. Use when you need to terminate a sponsorship relationship between a sponsor and a sponsorable entity. Either sponsor ID/login and sponsorable ID/login must be provided.

This action allows users to cancel an ongoing workflow run in a GitHub repository. It can be used when the workflow is currently in a cancellable state, like 'in_progress' or 'queued'. Note that cancellation is asynchronous - the API returns 202 Accepted to indicate the request was accepted, but the actual cancellation may take a moment to complete.

Check if the authenticated user is following a specified person on GitHub. Use this action when you need to verify whether the currently authenticated user follows another GitHub user. The action returns a boolean status and descriptive message.

This action checks whether you have starred a specific GitHub gist. It returns a clear boolean indicating the star status, making it easy to conditionally star or unstar gists.

This action checks whether a specified pull request in a GitHub repository has been merged. It verifies the merge status based on the HTTP response code returned by the GitHub API.

Checks if a pull request has been merged by querying the GitHub API. Use this action when you need to verify whether a specific pull request has been successfully merged into its target branch. The API returns a 204 status for merged PRs and 404 for unmerged PRs.

This action checks whether the authenticated user has starred a specific GitHub repository. It returns an indication of the star status, allowing users to know if the repository is part of their starred repositories.

This action checks if a specified user can be assigned to issues in a given GitHub repository. It verifies the assignability of the user based on the repository's permissions and returns an appropriate response.

This action checks whether a specified user has permission to be assigned to a specific issue in a GitHub repository. It can verify the assignment eligibility based on repository ownership and user permissions.

This action checks if a specified GitHub user is following another GitHub user. It returns a status of 204 if the user is following, and 404 if they are not or if the users are invalid.

Checks whether a specified GitHub user has been blocked by the currently authenticated user. It returns a 204 No Content response if the user is blocked, or a 404 Not Found if they are not.

This action checks if a specific GitHub user is blocked by a designated organization. Returns a clear is_blocked boolean indicating whether the user is blocked or not.

This action checks whether a specified user is a collaborator on a given GitHub repository. It returns a 204 status if the user is a collaborator, and a 404 status if the user is not a collaborator or if the repository or user does not exist.

This action verifies if the authenticated user follows a specific GitHub user. Returns a clear response indicating whether the user is being followed or not.

This action checks the private vulnerability reporting status of a specified repository. It determines whether the feature is enabled or not for the given owner and repository.

Tool to check if a user is a public member of an organization. Use when you need to verify public organization membership status.

Check if a repository is starred by the authenticated user. Use this action when you need to verify whether the authenticated user has starred a specific repository. This is useful for confirming star status before performing star/unstar operations or displaying repository status.

This action checks the access level of a specified team for a given project within an organization. It verifies if the team has read, write, or admin permissions and returns relevant project details if access is granted.

This action retrieves the permissions that a specific team has for a given repository within an organization. It checks both direct permissions and any inherited permissions from parent teams.

This action checks the validity of an OAuth access token for your GitHub OAuth App. It verifies the token's active status and retrieves details including scopes, permissions, and expiration. IMPORTANT: You must be the owner of the OAuth App (client_id) and provide a token issued by that app. This endpoint requires OAuth App credentials (client_id and client_secret) for authentication, not a personal access token.

Tool to clear the value of a field for an item in a GitHub Project V2. Use when you need to remove or reset a field value (text, number, date, assignees, labels, single-select, iteration, or milestone fields).

This action clears GitHub Actions caches for a specified repository based on the provided cache key. Optionally, it can narrow down the deletion to a specific Git reference such as a branch or pull request.

This action clears all custom labels assigned to a self-hosted runner belonging to a specific organization. Default labels will remain unaffected, ensuring the runner retains essential identification tags.

Close a GitHub issue by setting its state to closed. Use this action when you need to mark an issue as resolved or no longer relevant. Optionally specify a reason for closing (completed or not_planned) to provide context.

Closes an open pull request without merging it. The pull request state is set to "closed" and it can be reopened later if needed. Use this action when you want to reject or abandon a pull request without merging the proposed changes into the base branch. You must have write access to the repository to close pull requests.