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 "Forming calls with GraphQL."
AcceptEnterpriseAdministratorInvitationInput
Autogenerated input type of AcceptEnterpriseAdministratorInvitation.
AddDiscussionCommentInput
Autogenerated input type of AddDiscussionComment.
Input fields for AddDiscussionCommentInput
| 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. |
AddEnterpriseOrganizationMemberInput
Autogenerated input type of AddEnterpriseOrganizationMember.
Input fields for AddEnterpriseOrganizationMemberInput
| Name | Description |
|---|---|
| A unique identifier for the client performing the mutation. |
| The ID of the enterprise which owns the organization. |
| The ID of the organization the users will be added to. |
| The role to assign the users in the organization. |
| The IDs of the enterprise members to add. |
AddEnterpriseSupportEntitlementInput
Autogenerated input type of AddEnterpriseSupportEntitlement.
Input fields for AddEnterpriseSupportEntitlementInput
| 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. |
AddProjectCardInput
Autogenerated input type of AddProjectCard.
Input fields for AddProjectCardInput
| 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. |
AddProjectV2DraftIssueInput
Autogenerated input type of AddProjectV2DraftIssue.
Input fields for AddProjectV2DraftIssueInput
| 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. A project item can also be created by providing the URL of an Issue or Pull Request if you have access. |
AddPullRequestReviewCommentInput
Autogenerated input type of AddPullRequestReviewComment.
Input fields for AddPullRequestReviewCommentInput
| 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 for AddPullRequestReviewInput
| 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 for AddPullRequestReviewThreadInput
| 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 for AddReactionInput
| 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 for ApproveDeploymentsInput
| 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 for AuditLogOrder
| Name | Description |
|---|---|
| The ordering direction. |
| The field to order Audit Logs by. |
CancelSponsorshipInput
Autogenerated input type of CancelSponsorship.
Input fields for CancelSponsorshipInput
| 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 for ChangeUserStatusInput
| 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 for CheckAnnotationData
| 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 for CheckRunFilter
| 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 for CheckRunOutput
| 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. |