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.
AddDiscussionCommentInput
Autogenerated input type of AddDiscussionComment.
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. |
AddProjectDraftIssueInput
Autogenerated input type of AddProjectDraftIssue.
Input fields
| Name | Description |
|---|---|
| The IDs of the assignees of the draft issue. Upcoming Change on 2023-01-01 UTC
Description: |
| The body of the draft issue. Upcoming Change on 2023-01-01 UTC
Description: |
| A unique identifier for the client performing the mutation. |
| The ID of the Project to add the draft issue to. This field is required. Upcoming Change on 2023-01-01 UTC
Description: |
| The title of the draft issue. This field is required. Upcoming Change on 2023-01-01 UTC
Description: |
AddProjectNextItemInput
Autogenerated input type of AddProjectNextItem.
Input fields
| Name | Description |
|---|---|
| A unique identifier for the client performing the mutation. |
| The content id of the item (Issue or PullRequest). This field is required. Upcoming Change on 2023-01-01 UTC
Description: |
| The ID of the Project to add the item to. This field is required. Upcoming Change on 2023-01-01 UTC
Description: |
AddProjectV2DraftIssueInput
Autogenerated input type of AddProjectV2DraftIssue.
Input fields
| Name | Description |
|---|---|
| The IDs of the assignees of the draft issue. |
| The body of the draft issue. |
| A unique identifier for the client performing the mutation. |
| The ID of the Project to add the draft issue to. |
| The title of the draft issue. |
AddPullRequestReviewCommentInput
Autogenerated input type of AddPullRequestReviewComment.
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. |
AddPullRequestReviewInput
Autogenerated input type of AddPullRequestReview.
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. |
AddPullRequestReviewThreadInput
Autogenerated input type of AddPullRequestReviewThread.
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. |
AddReactionInput
Autogenerated input type of AddReaction.
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. |
ApproveDeploymentsInput
Autogenerated input type of ApproveDeployments.
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. |
AuditLogOrder
Ordering options for Audit Log connections.
Input fields
| Name | Description |
|---|---|
| The ordering direction. |
| The field to order Audit Logs by. |
CancelSponsorshipInput
Autogenerated input type of CancelSponsorship.
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. |
ChangeUserStatusInput
Autogenerated input type of ChangeUserStatus.
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. |
CheckAnnotationData
Information from a check run analysis to specific lines of code.
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. |
CheckRunFilter
The filters that are available when fetching check runs.
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 these conclusions. |
| Filters the check runs by this status. Superceded by statuses. |
| Filters the check runs by this status. Overrides status. |
CheckRunOutput
Descriptive details about the check run.
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. |
CloneProjectInput
Autogenerated input type of CloneProject.
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. |
CloneTemplateRepositoryInput
Autogenerated input type of CloneTemplateRepository.
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. |
CloseIssueInput
Autogenerated input type of CloseIssue.
Input fields
| Name | Description |
|---|---|
| A unique identifier for the client performing the mutation. |
| ID of the issue to be closed. |
| The reason the issue is to be closed. |
CommitContributionOrder
Ordering options for commit contribution connections.
Input fields
| Name | Description |
|---|---|
| The ordering direction. |
| The field by which to order commit contributions. |
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
repositoryNameWithOwner and branchName.
Examples
Specify a branch using a global node ID:
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }
Specify a branch using repositoryNameWithOwner and branchName:
{
"repositoryNameWithOwner": "github/graphql-client",
"branchName": "main"
}.
ContributionOrder
Ordering options for contribution connections.
Input fields
| Name | Description |
|---|---|
| The ordering direction. |
ConvertProjectCardNoteToIssueInput
Autogenerated input type of ConvertProjectCardNoteToIssue.
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. |