GitHub

Tools

• Accept a repository invitation

  Accepts a pending repository invitation that has been issued to the authenticated user.

• Add app access restrictions

  Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.

• Add a repository collaborator

  Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may b

• Add a repository to an app installation

  Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.

• Add a selected repository to a user secret

  Grants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.

• Add assignees to an issue

  Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.

• Add email for auth user

  Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the cur

• Add labels to an issue

  Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.

• Add org runner labels

  Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.

• Add or update team membership for a user

  Adds a github user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.

• Add or update team project permissions

  Grants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.

• Add or update team repository permissions

  Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.

• Add project collaborator

  Adds a specified github user as a collaborator to an existing organization project with a given permission level.

• Add repo to org secret with selected access

  Adds a repository to an existing organization-level github actions secret that is configured for 'selected' repository access.

• Add runner labels

  Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.

• Add selected repository to an organization secret

  Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.

• Add selected repository to an organization variable

  Grants a repository access to an organization-level github actions variable, if that variable's visibility is set to 'selected repositories'.

• Add selected repo to org secret

  Grants an existing repository access to an existing organization-level dependabot secret; the repository must belong to the organization, and the call succeeds without change if access already exists.

• Add social accounts for the authenticated user

  Adds one or more social media links (which must be valid, full urls for platforms supported by github) to the authenticated user's public github profile.

• Add status check contexts

  Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.

• Add team access restrictions

  Overwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.

• Add user access restrictions

  Sets/replaces list of users allowed to push to a protected branch; usernames (e.g., `["user1"]`) must be a json array in request body (not schema parameters), an empty array `[]` removes all restrictions.

• Add users to codespaces access for an organization

  Sets or replaces the list of organization members granted codespaces access billed to the organization; ensure the organization's billing settings allow access for selected members.

• Approve a workflow run for a fork pull request

  Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.

• Assign an organization role to a team

  Assigns an existing organization-level role (identified by `role id`) to a team (identified by `team slug`) within a github organization (`org`), provided the organization, team, and role already exist.

• Assign an organization role to a user

  Assigns a specific organization role to a user who is a member or an outside collaborator in a github organization, using a valid role id.

• Authuserdockerconflictpackageslist

  Lists docker packages for the authenticated user that encountered conflicts during the docker migration process.

• Block a user

  Blocks an existing individual github user (not an organization or your own account), preventing them from interacting with your account and repositories.

• Block a user from an organization

  Blocks an existing github user from an existing organization, preventing their contributions, collaboration, and forking of the organization's repositories.

• Cancel a GitHub Pages deployment

  Cancels an existing, ongoing or queued github pages deployment for a repository using its `pages deployment id`.

• Cancel a workflow run

  Cancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').

• Check a token

  Checks if a github app or oauth access token is valid for the specified client id and retrieves its details, typically to verify its active status and grants.

• Check if a gist is starred

  Checks if a gist, identified by `gist id`, is starred by the authenticated user, returning an empty response (204) if starred, or a 404 error if not starred or not found.

• Check if a user can be assigned

  Verifies if a github user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the response.

• Check if a user can be assigned to an issue

  Checks if a specified github user can be assigned to a given issue within a repository.

• Check if a user follows another user

  Checks if a github user `username` follows `target user`; returns a 204 http status if true, 404 if not or if users are invalid.

• Check if a user is a repository collaborator

  Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.

• Check if a user is blocked by an organization

  Checks if a github user is blocked by an organization; a successful response (204 no content) indicates the user is blocked, while a 404 not found error indicates the user is not blocked.

• Check if a user is blocked by the authenticated user

  Checks if the specified github user is blocked by the authenticated user; a 204 no content response indicates the user is blocked, while a 404 not found indicates they are not.

• Check if person is followed by authenticated user

  Checks if the authenticated github user follows a target github user; an http 204 status indicates the user is followed, while an http 404 status indicates the user is not followed or the target user does not exist.

• Check if pull request merged

  Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).

• Check if repo starred by auth user

  Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.g., http 404) if the repository is no

• Check private vulnerability reporting status

  Checks if private vulnerability reporting is enabled for the specified repository.

• Check team permissions for a project

  Checks if a team has 'read', 'write', or 'admin' permissions for an organization's specific classic project, returning the project's details if access is confirmed.

• Check team permissions for a repository

  Checks a team's permissions for a specific repository within an organization, including permissions inherited from parent teams.

• Clear repository cache by key

  Deletes github actions caches from a repository matching a specific `key` and an optional git `ref`, used to manage storage or clear outdated/corrupted caches; the action succeeds even if no matching caches are found to delete.

• Clear self-hosted runner org labels

  Removes all custom labels from a self-hosted runner for an organization; default labels (e.g., 'self-hosted', 'linux', 'x64') will remain.

• List repositories starred by the authenticated user

  Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.

• List stargazers

  Deprecated: lists users who have starred a repository; use `list stargazers` instead.

• Star a repository for the authenticated user

  Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

Works well with

How Switchy teams use it

Starter prompts

@GitHub list all open pull requests in the repository my-org/api-server and include the author and status checks for each

@GitHub create a new branch called feature/user-authentication in the repository my-org/web-app based on the main branch

@GitHub add the labels 'bug' and 'high-priority' to issue #42 in my-org/mobile-app and assign it to @jane

@GitHub show me the status of the most recent workflow run for the main branch in my-org/backend-service

@GitHub add the user contractor-username as a collaborator with push permission to the repository my-org/docs-site

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Use-case deep-dives

Frequently asked