Sobre objetos de entrada
Objetos de entrada podem ser descritos como "objetos estruturáveis", pois incluem um conjunto de campos de entrada que definem o objeto.
Por exemplo, CommitAuthor
toma um campo denominado e-mails
. Fornecer um valor para e-mails
transforma CommitAuthor
em uma lista de objetos de usuário
que contém esse endereço de e-mail. Observe que objetos pode ter objetos de entrada, enquanto mutações exigem objetos de entrada.
Para obter mais informações, consulte "Sobre mutações".
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 |
---|---|
|
The ordering direction. |
|
The field to order Audit Logs by. |
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 |
---|---|
|
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. |
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 |
---|---|
|
The ordering direction. |
|
The field by which to order commit contributions. |
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 |
---|---|
|
Can this branch be deleted. |
|
Are force pushes allowed on this branch. |
|
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. |
|
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 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 body of the content attachment, which may contain markdown. |
|
A unique identifier for the client performing the mutation. |
|
The node ID of the content_reference. |
|
The title of the content attachment. |
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 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 |
---|---|
|
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 content of the discussion. |
|
A unique identifier for the client performing the mutation. |
|
If true, restricts the visibility of this discussion to team members and organization admins. If false or not specified, allows any organization member to view this discussion. |
|
The ID of the team to which the discussion belongs. |
|
The title of the discussion. |
Preview notice
DeleteLabelInput
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. |
|
The Node ID of the label to be deleted. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order deployments by. |
DraftPullRequestReviewThread
Specifies a review comment thread to be left with a Pull Request Review.
Input fields
Name | Description |
---|---|
|
Body of the comment to leave. |
|
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 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 |
---|---|
|
The email address to associate with this merge. |
|
A unique identifier for the client performing the mutation. |
|
Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used. |
|
Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used. |
|
The merge method to use. If omitted, defaults to 'MERGE'. |
|
ID of the pull request to enable auto-merge on. |
EnterpriseAdministratorInvitationOrder
Ordering options for enterprise administrator invitation connections.
Input fields
Name | Description |
---|---|
|
The ordering direction. |
The field to order enterprise administrator invitations by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order enterprise members by. |
EnterpriseServerUserAccountEmailOrder
Ordering options for Enterprise Server user account email connections.
Input fields
Name | Description |
---|---|
|
The ordering direction. |
The field to order emails by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
The field to order user accounts by. |
EnterpriseServerUserAccountsUploadOrder
Ordering options for Enterprise Server user accounts upload connections.
Input fields
Name | Description |
---|---|
|
The ordering direction. |
The field to order user accounts uploads by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order repositories by. |
Input fields
Name | Description |
---|---|
|
The description of Project. |
|
A unique identifier for the client performing the mutation. |
|
A list of columns containing issues and pull requests. |
|
The name of Project. |
|
The name of the Organization or User to create the Project under. |
|
Whether the Project is public or not. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order IP allow list entries by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order issue comments by the specified field. |
|
The field in which to order issue comments by. |
Input fields
Name | Description |
---|---|
|
List issues assigned to given name. Pass in |
|
List issues created by given name. |
|
List issues where the list of label names exist on the issue. |
|
List issues where the given name is mentioned in the issue. |
|
List issues by given milestone argument. If an string representation of an
integer is passed, it should refer to a milestone by its number field. Pass in
|
|
List issues that have been updated at or after the given date. |
|
List issues filtered by the list of states given. |
|
List issues subscribed to by viewer. |
Input fields
Name | Description |
---|---|
|
The direction in which to order issues by the specified field. |
|
The field in which to order issues by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order labels by the specified field. |
|
The field in which to order labels by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order languages by. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
A reason for why the item will be locked. |
|
ID of the item to be locked. |
Input fields
Name | Description |
---|---|
|
The name of the base branch that the provided head will be merged into. |
|
A unique identifier for the client performing the mutation. |
|
Message to use for the merge commit. If omitted, a default will be used. |
|
The head to merge into the base branch. This can be a branch name or a commit GitObjectID. |
|
The Node ID of the Repository containing the base branch that will be modified. |
Input fields
Name | Description |
---|---|
|
The email address to associate with this merge. |
|
A unique identifier for the client performing the mutation. |
|
Commit body to use for the merge commit; if omitted, a default message will be used. |
|
Commit headline to use for the merge commit; if omitted, a default message will be used. |
|
OID that the pull request head ref must match to allow merge; if omitted, no check is performed. |
|
The merge method to use. If omitted, defaults to 'MERGE'. |
|
ID of the pull request to be merged. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order milestones by. |
Input fields
Name | Description |
---|---|
|
The classification of comment. |
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the subject to modify. |
Input fields
Name | Description |
---|---|
|
Place the new card after the card with this id. Pass null to place it at the top. |
|
The id of the card to move. |
|
A unique identifier for the client performing the mutation. |
|
The id of the column to move it into. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order organizations by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order package files by the specified field. |
|
The field in which to order package files by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order packages by the specified field. |
|
The field in which to order packages by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order package versions by the specified field. |
|
The field in which to order package versions by. |
Input fields
Name | Description |
---|---|
|
The name of the column. |
|
A list of issues and pull requests in the column. |
|
The position of the column, starting from 0. |
Input fields
Name | Description |
---|---|
|
The direction in which to order projects by the specified field. |
|
The field in which to order projects by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order pull requests by the specified field. |
|
The field in which to order pull requests by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order reactions by the specified field. |
|
The field in which to order reactions by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order refs by the specified field. |
|
The field in which to order refs by. |
Preview notice
RefUpdate
is available under the Update refs preview. During the preview period, the API may change without notice.
Input fields
Name | Description |
---|---|
|
The value this ref should be updated to. |
|
The value this ref needs to point to before the update. |
|
Force a non fast-forward update. |
|
The fully qualified name of the ref to be update. For example |
Input fields
Name | Description |
---|---|
|
The direction in which to order releases by the specified field. |
|
The field in which to order releases by. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The name of the emoji reaction to remove. |
|
The Node ID of the subject to modify. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order repository invitations by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order repositories by. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the pull request to modify. |
|
The Node IDs of the team to request. |
|
Add users to the set rather than replace. |
|
The Node IDs of the user to request. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order saved replies by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
Input fields
Name | Description |
---|---|
|
The direction in which to order nodes. |
|
The field in which to order nodes by. |
Input fields
Name | Description |
---|---|
|
The text field to set on the Pull Request Review. |
|
A unique identifier for the client performing the mutation. |
|
The event to send to the Pull Request Review. |
|
The Pull Request ID to submit any pending reviews. |
|
The Pull Request Review ID to submit. |
Input fields
Name | Description |
---|---|
|
The direction in which to order nodes. |
|
The field by which to order nodes. |
Input fields
Name | Description |
---|---|
|
The direction in which to order nodes. |
|
The field by which to order nodes. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order team members by. |
Input fields
Name | Description |
---|---|
|
The direction in which to order nodes. |
|
The field in which to order nodes by. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order repositories by. |
Input fields
Name | Description |
---|---|
|
ID of the issue or pull request currently considered canonical/authoritative/original. |
|
A unique identifier for the client performing the mutation. |
|
ID of the issue or pull request currently marked as a duplicate. |
Input fields
Name | Description |
---|---|
|
Can this branch be deleted. |
|
Are force pushes allowed on this branch. |
|
The global relay id of the branch protection rule to be updated. |
|
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. |
|
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. |
|
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 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. |
|
The node of the check. |
|
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 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 |
---|---|
|
The check suite preferences to modify. |
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the repository. |
UpdateEnterpriseAllowPrivateRepositoryForkingSettingInput
Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the allow private repository forking setting. |
|
The value for the allow private repository forking setting on the enterprise. |
UpdateEnterpriseDefaultRepositoryPermissionSettingInput
Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the default repository permission setting. |
|
The value for the default repository permission setting on the enterprise. |
UpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput
Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can change repository visibility setting. |
|
The value for the members can change repository visibility setting on the enterprise. |
UpdateEnterpriseMembersCanCreateRepositoriesSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can create repositories setting. |
|
Allow members to create internal repositories. Defaults to current value. |
|
Allow members to create private repositories. Defaults to current value. |
|
Allow members to create public repositories. Defaults to current value. |
|
When false, allow member organizations to set their own repository creation member privileges. |
|
Value for the members can create repositories setting on the enterprise. This or the granular public/private/internal allowed fields (but not both) must be provided. |
UpdateEnterpriseMembersCanDeleteIssuesSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can delete issues setting. |
|
The value for the members can delete issues setting on the enterprise. |
UpdateEnterpriseMembersCanDeleteRepositoriesSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can delete repositories setting. |
|
The value for the members can delete repositories setting on the enterprise. |
UpdateEnterpriseMembersCanInviteCollaboratorsSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can invite collaborators setting. |
|
The value for the members can invite collaborators setting on the enterprise. |
UpdateEnterpriseMembersCanMakePurchasesSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can make purchases setting. |
|
The value for the members can make purchases setting on the enterprise. |
UpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can update protected branches setting. |
|
The value for the members can update protected branches setting on the enterprise. |
UpdateEnterpriseMembersCanViewDependencyInsightsSettingInput
Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the members can view dependency insights setting. |
|
The value for the members can view dependency insights setting on the enterprise. |
UpdateEnterpriseOrganizationProjectsSettingInput
Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the organization projects setting. |
|
The value for the organization projects setting on the enterprise. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The description of the enterprise. |
|
The Enterprise ID to update. |
|
The location of the enterprise. |
|
The name of the enterprise. |
|
The URL of the enterprise's website. |
UpdateEnterpriseRepositoryProjectsSettingInput
Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the repository projects setting. |
|
The value for the repository projects setting on the enterprise. |
UpdateEnterpriseTeamDiscussionsSettingInput
Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the team discussions setting. |
|
The value for the team discussions setting on the enterprise. |
UpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput
Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the enterprise on which to set the two factor authentication required setting. |
|
The value for the two factor authentication required setting on the enterprise. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The ID of the owner on which to set the IP allow list enabled setting. |
|
The value for the IP allow list enabled setting. |
Input fields
Name | Description |
---|---|
|
An IP address or range of addresses in CIDR notation. |
|
A unique identifier for the client performing the mutation. |
|
The ID of the IP allow list entry to update. |
|
Whether the IP allow list entry is active when an IP allow list is enabled. |
|
An optional name for the IP allow list entry. |
Input fields
Name | Description |
---|---|
|
An array of Node IDs of users for this issue. |
|
The body for the issue description. |
|
A unique identifier for the client performing the mutation. |
|
The ID of the Issue to modify. |
|
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 desired issue state. |
|
The title for the issue. |
Preview notice
UpdateLabelInput
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 updated color of the label. |
|
A brief description of the label, such as its purpose. |
|
The Node ID of the label to be updated. |
|
The updated name of the label. |
Input fields
Name | Description |
---|---|
|
The description of project. |
|
A unique identifier for the client performing the mutation. |
|
The name of project. |
|
The Project ID to update. |
|
Whether the project is public or not. |
|
Whether the project is open or closed. |
Input fields
Name | Description |
---|---|
|
An array of Node IDs of users for this pull request. |
|
The name of the branch you want your changes pulled into. This should be an existing branch on the current repository. |
|
The contents of the pull request. |
|
A unique identifier for the client performing the mutation. |
|
An array of Node IDs of labels for this pull request. |
|
Indicates whether maintainers can modify the pull request. |
|
The Node ID of the milestone for this pull request. |
|
An array of Node IDs for projects associated with this pull request. |
|
The Node ID of the pull request. |
|
The target state of the pull request. |
|
The title of the pull request. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
Permit updates of branch Refs that are not fast-forwards?. |
|
The GitObjectID that the Ref shall be updated to target. |
|
The Node ID of the Ref to be updated. |
Preview notice
UpdateRefsInput
is available under the Update refs 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 list of ref updates. |
|
The Node ID of the repository. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
A new description for the repository. Pass an empty string to erase the existing description. |
|
Indicates if the repository should have the issues feature enabled. |
|
Indicates if the repository should have the project boards feature enabled. |
|
Indicates if the repository should have the wiki feature enabled. |
|
The URL for a web page about this repository. Pass an empty string to erase the existing URL. |
|
The new name of the repository. |
|
The ID of the repository to update. |
|
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. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The new state of the subscription. |
|
The Node ID of the subscribable object to modify. |
Input fields
Name | Description |
---|---|
|
The updated text of the discussion. |
|
The current version of the body content. If provided, this update operation will be rejected if the given version does not match the latest version on the server. |
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the discussion to modify. |
|
If provided, sets the pinned state of the updated discussion. |
|
The updated title of the discussion. |
Preview notice
UpdateTeamReviewAssignmentInput
is available under the Team review assignments preview. During the preview period, the API may change without notice.
Input fields
Name | Description |
---|---|
|
The algorithm to use for review assignment. |
|
A unique identifier for the client performing the mutation. |
|
Turn on or off review assignment. |
|
An array of team member IDs to exclude. |
|
The Node ID of the team to update review assignments of. |
|
Notify the entire team of the PR if it is delegated. |
|
The number of team members to assign. |
Input fields
Name | Description |
---|---|
|
A unique identifier for the client performing the mutation. |
|
The Node ID of the repository. |
|
An array of topic names. |
Input fields
Name | Description |
---|---|
|
The ordering direction. |
|
The field to order user statuses by. |