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."
AddAssigneesToAssignableInput
Autogenerated input type of AddAssigneesToAssignable.
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. |
AddCommentInput
Autogenerated input type of AddComment.
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. |
AddEnterpriseAdminInput
Autogenerated input type of AddEnterpriseAdmin.
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise account to which the administrator should be added. |
|
The login of the user to add as an administrator. |
AddLabelsToLabelableInput
Autogenerated input type of AddLabelsToLabelable.
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. |
AddProjectCardInput
Autogenerated input type of AddProjectCard.
Input fields
| Name | Description |
|---|---|
|
A unique identifier for the client performing the mutation. |
|