About input objects
Input objects can be described as "composable objects" because they include a set of input fields that define the object.
For example, CommitAuthor takes a field called emails. Providing a value for emails transforms CommitAuthor into a list of User objects containing that email address. Note that objects may have input objects, whereas mutations require input objects.
For more information, see "About mutations."
AcceptEnterpriseAdministratorInvitationInput
Autogenerated input type of AcceptEnterpriseAdministratorInvitation.
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The id of the invitation being accepted. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The name of the suggested topic. |
|
The Node ID of the repository. |
Input fields
| Name | Description |
|---|---|
|
The id of the assignable object to add assignees to. |
|
The id of users to add as assignees. |
|
A unique identifier for the client performing the mutation. |
Input fields
| Name | Description |
|---|---|
|
The contents of the comment. |
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the subject to modify. |
Input fields
| Name | Description |
|---|---|
|
The contents of the comment. |
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the discussion to comment on. |
|
The Node ID of the discussion comment within this discussion to reply to. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the Enterprise which the admin belongs to. |
|
The login of a member who will receive the support entitlement. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The ids of the labels to add. |
|
The id of the labelable object to add labels to. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The content of the card. Must be a member of the ProjectCardItem union. |
|
The note on the card. |
|
The Node ID of the ProjectColumn. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The name of the column. |
|
The Node ID of the project. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The content id of the item (Issue or PullRequest). |
|
The ID of the Project to add the item to. |
Input fields
| Name | Description |
|---|---|
|
The text of the comment. |
|
A unique identifier for the client performing the mutation. |
|
The SHA of the commit to comment on. |
|
The comment id to reply to. |
|
The relative path of the file to comment on. |
|
The line index in the diff to comment on. |
|
The node ID of the pull request reviewing. |
|
The Node ID of the review to modify. |
Input fields
| Name | Description |
|---|---|
|
The contents of the review body comment. |
|
A unique identifier for the client performing the mutation. |
|
The review line comments. |
|
The commit OID the review pertains to. |
|
The event to perform on the pull request review. |
|
The Node ID of the pull request to modify. |
|
The review line comment threads. |
Input fields
| Name | Description |
|---|---|
|
Body of the thread's first comment. |
|
A unique identifier for the client performing the mutation. |
|
The line of the blob to which the thread refers. The end of the line range for multi-line comments. |
|
Path to the file being commented on. |
|
The node ID of the pull request reviewing. |
|
The Node ID of the review to modify. |
|
The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range. |
|
The first line of the range to which the comment refers. |
|
The side of the diff on which the start line resides. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The name of the emoji to react with. |
|
The Node ID of the subject to modify. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The Starrable ID to star. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the discussion or comment to upvote. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The URL of the domain. |
|
The ID of the owner to add the domain to. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
Optional comment for approving deployments. |
|
The ids of environments to reject deployments. |
|
The node ID of the workflow run containing the pending deployments. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the verifiable domain to approve. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the repository to mark as archived. |
Input fields
| Name | Description |
|---|---|
|
The ordering direction. |
|
The field to order Audit Logs by. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the pending enterprise administrator invitation. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the user or organization who is acting as the sponsor, paying for the sponsorship. Required if sponsorLogin is not given. |
|
The username of the user or organization who is acting as the sponsor, paying for the sponsorship. Required if sponsorId is not given. |
|
The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given. |
|
The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀. |
|
If set, the user status will not be shown after this date. |
|
Whether this status should indicate you are not fully available on GitHub, e.g., you are away. |
|
A short description of your current status. |
|
The ID of the organization whose members will be allowed to see the status. If omitted, the status will be publicly visible. |
Input fields
| Name | Description |
|---|---|
|
Represents an annotation's information level. |
|
The location of the annotation. |
|
A short description of the feedback for these lines of code. |
|
The path of the file to add an annotation to. |
|
Details about this annotation. |
|
The title that represents the annotation. |
Input fields
| Name | Description |
|---|---|
|
The ending column of the range. |
|
The ending line of the range. |
|
The starting column of the range. |
|
The starting line of the range. |
Input fields
| Name | Description |
|---|---|
|
A short explanation of what this action would do. |
|
A reference for the action on the integrator's system. |
|
The text to be displayed on a button in the web UI. |
Input fields
| Name | Description |
|---|---|
|
Filters the check runs created by this application ID. |
|
Filters the check runs by this name. |
|
Filters the check runs by this type. |
|
Filters the check runs by this status. |
Input fields
| Name | Description |
|---|---|
|
The annotations that are made as part of the check run. |
|
Images attached to the check run output displayed in the GitHub pull request UI. |
|
The summary of the check run (supports Commonmark). |
|
The details of the check run (supports Commonmark). |
|
A title to provide for this check run. |
CheckRunOutputImage
Images attached to the check run output displayed in the GitHub pull request UI.
Input fields
| Name | Description |
|---|---|
|
The alternative text for the image. |
|
A short image description. |
|
The full URL of the image. |
Input fields
| Name | Description |
|---|---|
|
The node ID of the application that owns the check suite. |
|
Set to |
Input fields
| Name | Description |
|---|---|
|
Filters the check suites created by this application ID. |
|
Filters the check suites by this name. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The id of the labelable object to clear the labels from. |
Input fields
| Name | Description |
|---|---|
|
The description of the project. |
|
A unique identifier for the client performing the mutation. |
|
Whether or not to clone the source project's workflows. |
|
The name of the project. |
|
The visibility of the project, defaults to false (private). |
|
The source project to clone. |
|
The owner ID to create the project under. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
A short description of the new repository. |
|
Whether to copy all branches from the template to the new repository. Defaults to copying only the default branch of the template. |
|
The name of the new repository. |
|
The ID of the owner for the new repository. |
|
The Node ID of the template repository. |
|
Indicates the repository's visibility level. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
ID of the issue to be closed. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
ID of the pull request to be closed. |
Input fields
| Name | Description |
|---|---|
|
Email addresses to filter by. Commits authored by any of the specified email addresses will be returned. |
|
ID of a User to filter by. If non-null, only commits authored by this user will be returned. This field takes precedence over emails. |
Input fields
| Name | Description |
|---|---|
|
The ordering direction. |
|
The field by which to order commit contributions. |
Input fields
| Name | Description |
|---|---|
|
The body of the message. |
|
The headline of the message. |
CommittableBranch
A git ref for a commit to be appended to.
The ref must be a branch, i.e. its fully qualified name must start
with refs/heads/ (although the input is not required to be fully
qualified).
The Ref may be specified by its global node ID or by the repository nameWithOwner and branch name.
Examples
Specify a branch using a global node ID:
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }
Specify a branch using nameWithOwner and branch name:
{
"nameWithOwner": "github/graphql-client",
"branchName": "main"
}.
Input fields
| Name | Description |
|---|---|
|
The unqualified name of the branch to append the commit to. |
|
The Node ID of the Ref to be updated. |
|
The nameWithOwner of the repository to commit to. |
Input fields
| Name | Description |
|---|---|
|
The ordering direction. |
Input fields
| Name | Description |
|---|---|
|
The body of the newly created issue. |
|
A unique identifier for the client performing the mutation. |
|
The ProjectCard ID to convert. |
|
The ID of the repository to create the issue in. |
|
The title of the newly created issue. Defaults to the card's note text. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
ID of the pull request to convert to draft. |
Input fields
| Name | Description |
|---|---|
|
Can this branch be deleted. |
|
Are force pushes allowed on this branch. |
|
A list of User or Team IDs allowed to bypass pull requests targeting matching branches. |
|
A unique identifier for the client performing the mutation. |
|
Will new commits pushed to matching branches dismiss pull request review approvals. |
|
Can admins overwrite branch protection. |
|
The glob-like pattern used to determine matching branches. |
|
A list of User, Team or App IDs allowed to push to matching branches. |
|
The global relay id of the repository in which a new branch protection rule should be created in. |
|
Number of approving reviews required to update matching branches. |
|
List of required status check contexts that must pass for commits to be accepted to matching branches. |
|
The list of required status checks. |
|
Are approving reviews required to update matching branches. |
|
Are reviews from code owners required to update matching branches. |
|
Are commits required to be signed. |
|
Are conversations required to be resolved before merging. |
|
Are merge commits prohibited from being pushed to this branch. |
|
Are status checks required to update matching branches. |
|
Are branches required to be up to date before merging. |
|
Is pushing to matching branches restricted. |
|
Is dismissal of pull request reviews restricted. |
|
A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches. |
Input fields
| Name | Description |
|---|---|
|
Possible further actions the integrator can perform, which a user may trigger. |
|
A unique identifier for the client performing the mutation. |
|
The time that the check run finished. |
|
The final conclusion of the check. |
|
The URL of the integrator's site that has the full details of the check. |
|
A reference for the run on the integrator's system. |
|
The SHA of the head commit. |
|
The name of the check. |
|
Descriptive details about the run. |
|
The node ID of the repository. |
|
The time that the check run began. |
|
The current status. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The SHA of the head commit. |
|
The Node ID of the repository. |
Input fields
| Name | Description |
|---|---|
|
The Ref to be updated. Must be a branch. |
|
A unique identifier for the client performing the mutation. |
|
The git commit oid expected at the head of the branch prior to the commit. |
|
A description of changes to files in this commit. |
|
The commit message the be included with the commit. |
Preview notice
CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.
Input fields
| Name | Description |
|---|---|
|
Attempt to automatically merge the default branch into the requested ref, defaults to true. |
|
A unique identifier for the client performing the mutation. |
|
Short description of the deployment. |
|
Name for the target deployment environment. |
|
JSON payload with extra information about the deployment. |
|
The node ID of the ref to be deployed. |
|
The node ID of the repository. |
|
The status contexts to verify against commit status checks. To bypass required contexts, pass an empty array. Defaults to all unique contexts. |
|
Specifies a task to execute. |
Preview notice
CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.
Input fields
| Name | Description |
|---|---|
|
Adds a new inactive status to all non-transient, non-production environment deployments with the same repository and environment name as the created status's deployment. |
|
A unique identifier for the client performing the mutation. |
|
The node ID of the deployment. |
|
A short description of the status. Maximum length of 140 characters. |
|
If provided, updates the environment of the deploy. Otherwise, does not modify the environment. |
|
Sets the URL for accessing your environment. |
|
The log URL to associate with this status. This URL should contain output to keep the user updated while the task is running or serve as historical information for what happened in the deployment. |
|
The state of the deployment. |
Input fields
| Name | Description |
|---|---|
|
The body of the discussion. |
|
The id of the discussion category to associate with this discussion. |
|
A unique identifier for the client performing the mutation. |
|
The id of the repository on which to create the discussion. |
|
The title of the discussion. |
Input fields
| Name | Description |
|---|---|
|
The logins for the administrators of the new organization. |
|
The email used for sending billing receipts. |
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise owning the new organization. |
|
The login of the new organization. |
|
The profile name of the new organization. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The name of the environment. |
|
The node ID of the repository. |
Input fields
| Name | Description |
|---|---|
|
An IP address or range of addresses in CIDR notation. |
|
A unique identifier for the client performing the mutation. |
|
Whether the IP allow list entry is active when an IP allow list is enabled. |
|
An optional name for the IP allow list entry. |
|
The ID of the owner for which to create the new IP allow list entry. |
Input fields
| Name | Description |
|---|---|
|
The Node ID for the user assignee for this issue. |
|
The body for the issue description. |
|
A unique identifier for the client performing the mutation. |
|
The name of an issue template in the repository, assigns labels and assignees from the template to the issue. |
|
An array of Node IDs of labels for this issue. |
|
The Node ID of the milestone for this issue. |
|
An array of Node IDs for projects associated with this issue. |
|
The Node ID of the repository. |
|
The title for the issue. |
Preview notice
CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
A 6 character hex code, without the leading #, identifying the color of the label. |
|
A brief description of the label, such as its purpose. |
|
The name of the label. |
|
The Node ID of the repository. |
Input fields
| Name | Description |
|---|---|
|
The description of project. |
|
A unique identifier for the client performing the mutation. |
|
The name of project. |
|
The owner ID to create the project under. |
|
A list of repository IDs to create as linked repositories for the project. |
|
The name of the GitHub-provided template. |
Input fields
| Name | Description |
|---|---|
|
The name of the branch you want your changes pulled into. This should be an existing branch on the current repository. You cannot update the base branch on a pull request to point to another repository. |
|
The contents of the pull request. |
|
A unique identifier for the client performing the mutation. |
|
Indicates whether this pull request should be a draft. |
|
The name of the branch where your changes are implemented. For cross-repository pull requests
in the same network, namespace |
|
Indicates whether maintainers can modify the pull request. |
|
The Node ID of the repository. |
|
The title of the pull request. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The fully qualified name of the new Ref (ie: |
|
The GitObjectID that the new Ref shall target. Must point to a commit. |
|
The Node ID of the Repository to create the Ref in. |
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
A short description of the new repository. |
|
Indicates if the repository should have the issues feature enabled. |
|
Indicates if the repository should have the wiki feature enabled. |
|
The URL for a web page about this repository. |
|
The name of the new repository. |
|
The ID of the owner for the new repository. |
|
When an organization is specified as the owner, this ID identifies the team that should be granted access to the new repository. |
|
Whether this repository should be marked as a template such that anyone who can access it can create new repositories with the same files and directory structure. |
|
Indicates the repository's visibility level. |
Input fields
| Name | Description |
|---|---|
|
The amount to pay to the sponsorable in US dollars. Required if a tierId is not specified. Valid values: 1-12000. |
|
A unique identifier for the client performing the mutation. |
|
Whether the sponsorship should happen monthly/yearly or just this one time. Required if a tierId is not specified. |
|
Specify whether others should be able to see that the sponsor is sponsoring the sponsorable. Public visibility still does not reveal which tier is used. |
|
Whether the sponsor should receive email updates from the sponsorable. |
|
The ID of the user or organization who is acting as the sponsor, paying for the sponsorship. Required if sponsorLogin is not g |