GitHub

• 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 repo to org secret with selected visibility

  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 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 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…

• 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…

• 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.

• Auth user docker conflict packages list

  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 person is followed by the 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…

• Check if a pull request has been 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 a repository is starred by the authenticated 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…

• 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 a 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 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…

• 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.

• Compare two commits

  Compares two commit points (commits, branches, tags, or shas) within a repository or across forks, using `base...head` or `owner:ref...owner:ref` format for the `basehead` parameter.

• Configure jitrunner for org

  Generates a jit configuration for a github organization's new self-hosted runner to run a single job then unregister; the runner group id must exist.

• Configure oidcsubject claim template

  Sets or updates the oidc subject claim customization template for an existing github organization by specifying which claims (e.g., 'repo', 'actor') form the oidc token's subject (`sub`).

• Convert an organization member to outside collaborator

  Converts an existing organization member, who is not an owner, to an outside collaborator, restricting their access to explicitly granted repositories.

• Create a blob

  Creates a git blob in a repository, requiring content and encoding ('utf-8' or 'base64').

• Create a check run

  Creates a new check run for a specific commit in a repository, used by external services to report status, detailed feedback, annotations, and images directly within the github ui.

• Create a check suite

  Creates a new check suite for a specific commit (`head sha`) in an original repository (not a fork); github dispatches a `check suite` webhook event with the `requested` action upon success.

• Create a codespace for the authenticated user

  Creates a github codespace for the authenticated user, requiring a json request body with either `repository id` (integer) or a `pull request` object (containing `pull request number` (integer) and…

• Create a codespace from a pull request

  Creates a github codespace for an open pull request in a codespaces-enabled repository, with options to customize its configuration.

• Create a codespace in a repository

  Creates a github codespace for the authenticated user in a specified repository, which must be accessible and use a valid `devcontainer.json` if `devcontainer path` is specified.

• Create a commit

  Creates a new commit in a github repository; the `tree` sha and any `parents` shas must already exist in the repository.

• Create a commit comment

  Creates a comment on a specific commit, or on a specific line if `path` and `position` are provided.

• Create a commit status

  Sets a commit's status (e.g., error, failure, pending, success from ci/cd) for a given sha; max 1000 statuses per sha/context.

And 763 more in Definable.