Sobre os enumeradores
Enumeradores representam possíveis conjuntos de valores para um campo.
Por exemplo, o objeto problema tem um campo denominado estado. O estado é um enumerador (especificamente, do tipo IssueState), porque pode estar ABERTO ou FECHADO.
Para obter mais informações, consulte "Introdução ao GraphQL".
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order audit log entries by timestamp.</p></p>
<h4>Valores</h4>
<p><strong>FAILURE</strong></p>
<p><p>An annotation indicating an inescapable error.</p></p>
<p><strong>NOTICE</strong></p>
<p><p>An annotation indicating some information.</p></p>
<p><strong>WARNING</strong></p>
<p><p>An annotation indicating an ignorable error.</p></p>
<h4>Valores</h4>
<p><strong>ACTION_REQUIRED</strong></p>
<p><p>The check suite or run requires action.</p></p>
<p><strong>CANCELLED</strong></p>
<p><p>The check suite or run has been cancelled.</p></p>
<p><strong>FAILURE</strong></p>
<p><p>The check suite or run has failed.</p></p>
<p><strong>NEUTRAL</strong></p>
<p><p>The check suite or run was neutral.</p></p>
<p><strong>SKIPPED</strong></p>
<p><p>The check suite or run was skipped.</p></p>
<p><strong>STALE</strong></p>
<p><p>The check suite or run was marked stale by GitHub. Only GitHub can use this conclusion.</p></p>
<p><strong>STARTUP_FAILURE</strong></p>
<p><p>The check suite or run has failed at startup.</p></p>
<p><strong>SUCCESS</strong></p>
<p><p>The check suite or run has succeeded.</p></p>
<p><strong>TIMED_OUT</strong></p>
<p><p>The check suite or run has timed out.</p></p>
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>Every check run available.</p></p>
<p><strong>LATEST</strong></p>
<p><p>The latest check run.</p></p>
<h4>Valores</h4>
<p><strong>COMPLETED</strong></p>
<p><p>The check suite or run has been completed.</p></p>
<p><strong>IN_PROGRESS</strong></p>
<p><p>The check suite or run is in progress.</p></p>
<p><strong>PENDING</strong></p>
<p><p>The check suite or run is in pending state.</p></p>
<p><strong>QUEUED</strong></p>
<p><p>The check suite or run has been queued.</p></p>
<p><strong>REQUESTED</strong></p>
<p><p>The check suite or run has been requested.</p></p>
<p><strong>WAITING</strong></p>
<p><p>The check suite or run is in waiting state.</p></p>
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>All collaborators the authenticated user can see.</p></p>
<p><strong>DIRECT</strong></p>
<p><p>All collaborators with permissions to an organization-owned subject, regardless of organization membership status.</p></p>
<p><strong>OUTSIDE</strong></p>
<p><p>All outside collaborators of an organization-owned subject.</p></p>
<h4>Valores</h4>
<p><strong>COLLABORATOR</strong></p>
<p><p>Author has been invited to collaborate on the repository.</p></p>
<p><strong>CONTRIBUTOR</strong></p>
<p><p>Author has previously committed to the repository.</p></p>
<p><strong>FIRST_TIMER</strong></p>
<p><p>Author has not previously committed to GitHub.</p></p>
<p><strong>FIRST_TIME_CONTRIBUTOR</strong></p>
<p><p>Author has not previously committed to the repository.</p></p>
<p><strong>MANNEQUIN</strong></p>
<p><p>Author is a placeholder for an unclaimed user.</p></p>
<p><strong>MEMBER</strong></p>
<p><p>Author is a member of the organization that owns the repository.</p></p>
<p><strong>NONE</strong></p>
<p><p>Author has no association with the repository.</p></p>
<p><strong>OWNER</strong></p>
<p><p>Author is the owner of the repository.</p></p>
<h4>Valores</h4>
<p><strong>ARCHIVED</strong></p>
<p><p>Unable to create comment because repository is archived.</p></p>
<p><strong>DENIED</strong></p>
<p><p>You cannot update this comment.</p></p>
<p><strong>INSUFFICIENT_ACCESS</strong></p>
<p><p>You must be the author or have write access to this repository to update this comment.</p></p>
<p><strong>LOCKED</strong></p>
<p><p>Unable to create comment because issue is locked.</p></p>
<p><strong>LOGIN_REQUIRED</strong></p>
<p><p>You must be logged in to update this comment.</p></p>
<p><strong>MAINTENANCE</strong></p>
<p><p>Repository is under maintenance.</p></p>
<p><strong>VERIFIED_EMAIL_REQUIRED</strong></p>
<p><p>At least one email address must be verified to update this comment.</p></p>
<h4>Valores</h4>
<p><strong>COMMIT_COUNT</strong></p>
<p><p>Order commit contributions by how many commits they represent.</p></p>
<p><strong>OCCURRED_AT</strong></p>
<p><p>Order commit contributions by when they were made.</p></p>
<h4>Valores</h4>
<p><strong>FIRST_QUARTILE</strong></p>
<p><p>Lowest 25% of days of contributions.</p></p>
<p><strong>FOURTH_QUARTILE</strong></p>
<p><p>Highest 25% of days of contributions. More contributions than the third quartile.</p></p>
<p><strong>NONE</strong></p>
<p><p>No contributions occurred.</p></p>
<p><strong>SECOND_QUARTILE</strong></p>
<p><p>Second lowest 25% of days of contributions. More contributions than the first quartile.</p></p>
<p><strong>THIRD_QUARTILE</strong></p>
<p><p>Second highest 25% of days of contributions. More contributions than second quartile, less than the fourth quartile.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Can read, write, and administrate repos by default.</p></p>
<p><strong>NONE</strong></p>
<p><p>No access.</p></p>
<p><strong>READ</strong></p>
<p><p>Can read repos by default.</p></p>
<p><strong>WRITE</strong></p>
<p><p>Can read and write repos by default.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order collection by creation time.</p></p>
<h4>Valores</h4>
<p><strong>REQUIRED_REVIEWERS</strong></p>
<p><p>Required reviewers.</p></p>
<p><strong>WAIT_TIMER</strong></p>
<p><p>Wait timer.</p></p>
<h4>Valores</h4>
<p><strong>APPROVED</strong></p>
<p><p>The deployment was approved.</p></p>
<p><strong>REJECTED</strong></p>
<p><p>The deployment was rejected.</p></p>
<h4>Valores</h4>
<p><strong>ABANDONED</strong></p>
<p><p>The pending deployment was not updated after 30 minutes.</p></p>
<p><strong>ACTIVE</strong></p>
<p><p>The deployment is currently active.</p></p>
<p><strong>DESTROYED</strong></p>
<p><p>An inactive transient deployment.</p></p>
<p><strong>ERROR</strong></p>
<p><p>The deployment experienced an error.</p></p>
<p><strong>FAILURE</strong></p>
<p><p>The deployment has failed.</p></p>
<p><strong>INACTIVE</strong></p>
<p><p>The deployment is inactive.</p></p>
<p><strong>IN_PROGRESS</strong></p>
<p><p>The deployment is in progress.</p></p>
<p><strong>PENDING</strong></p>
<p><p>The deployment is pending.</p></p>
<p><strong>QUEUED</strong></p>
<p><p>The deployment has queued.</p></p>
<p><strong>WAITING</strong></p>
<p><p>The deployment is waiting.</p></p>
<h4>Valores</h4>
<p><strong>ERROR</strong></p>
<p><p>The deployment experienced an error.</p></p>
<p><strong>FAILURE</strong></p>
<p><p>The deployment has failed.</p></p>
<p><strong>INACTIVE</strong></p>
<p><p>The deployment is inactive.</p></p>
<p><strong>IN_PROGRESS</strong></p>
<p><p>The deployment is in progress.</p></p>
<p><strong>PENDING</strong></p>
<p><p>The deployment is pending.</p></p>
<p><strong>QUEUED</strong></p>
<p><p>The deployment is queued.</p></p>
<p><strong>SUCCESS</strong></p>
<p><p>The deployment was successful.</p></p>
<p><strong>WAITING</strong></p>
<p><p>The deployment is waiting.</p></p>
<h4>Valores</h4>
<p><strong>LEFT</strong></p>
<p><p>The left side of the diff.</p></p>
<p><strong>RIGHT</strong></p>
<p><p>The right side of the diff.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order discussions by creation time.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order discussions by most recent modification time.</p></p>
EnterpriseAdministratorInvitationOrderField
Properties by which enterprise administrator invitation connections can be ordered.
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order enterprise administrator member invitations by creation time.</p></p>
<h4>Valores</h4>
<p><strong>BILLING_MANAGER</strong></p>
<p><p>Represents a billing manager of the enterprise account.</p></p>
<p><strong>OWNER</strong></p>
<p><p>Represents an owner of the enterprise account.</p></p>
EnterpriseDefaultRepositoryPermissionSettingValue
The possible values for the enterprise base repository permission setting.
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Organization members will be able to clone, pull, push, and add new collaborators to all organization repositories.</p></p>
<p><strong>NONE</strong></p>
<p><p>Organization members will only be able to clone and pull public repositories.</p></p>
<p><strong>NO_POLICY</strong></p>
<p><p>Organizations in the enterprise choose base repository permissions for their members.</p></p>
<p><strong>READ</strong></p>
<p><p>Organization members will be able to clone and pull all organization repositories.</p></p>
<p><strong>WRITE</strong></p>
<p><p>Organization members will be able to clone, pull, and push all organization repositories.</p></p>
EnterpriseEnabledDisabledSettingValue
The possible values for an enabled/disabled enterprise setting.
<h4>Valores</h4>
<p><strong>DISABLED</strong></p>
<p><p>The setting is disabled for organizations in the enterprise.</p></p>
<p><strong>ENABLED</strong></p>
<p><p>The setting is enabled for organizations in the enterprise.</p></p>
<p><strong>NO_POLICY</strong></p>
<p><p>There is no policy set for organizations in the enterprise.</p></p>
<h4>Valores</h4>
<p><strong>ENABLED</strong></p>
<p><p>The setting is enabled for organizations in the enterprise.</p></p>
<p><strong>NO_POLICY</strong></p>
<p><p>There is no policy set for organizations in the enterprise.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order enterprise members by creation time.</p></p>
<p><strong>LOGIN</strong></p>
<p><p>Order enterprise members by login.</p></p>
EnterpriseMembersCanCreateRepositoriesSettingValue
The possible values for the enterprise members can create repositories setting.
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>Members will be able to create public and private repositories.</p></p>
<p><strong>DISABLED</strong></p>
<p><p>Members will not be able to create public or private repositories.</p></p>
<p><strong>NO_POLICY</strong></p>
<p><p>Organization administrators choose whether to allow members to create repositories.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>Members will be able to create only private repositories.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>Members will be able to create only public repositories.</p></p>
EnterpriseMembersCanMakePurchasesSettingValue
The possible values for the members can make purchases setting.
<h4>Valores</h4>
<p><strong>DISABLED</strong></p>
<p><p>The setting is disabled for organizations in the enterprise.</p></p>
<p><strong>ENABLED</strong></p>
<p><p>The setting is enabled for organizations in the enterprise.</p></p>
EnterpriseServerUserAccountEmailOrderField
Properties by which Enterprise Server user account email connections can be ordered.
<h4>Valores</h4>
<p><strong>EMAIL</strong></p>
<p><p>Order emails by email.</p></p>
EnterpriseServerUserAccountOrderField
Properties by which Enterprise Server user account connections can be ordered.
<h4>Valores</h4>
<p><strong>LOGIN</strong></p>
<p><p>Order user accounts by login.</p></p>
<p><strong>REMOTE_CREATED_AT</strong></p>
<p><p>Order user accounts by creation time on the Enterprise Server installation.</p></p>
EnterpriseServerUserAccountsUploadOrderField
Properties by which Enterprise Server user accounts upload connections can be ordered.
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order user accounts uploads by creation time.</p></p>
EnterpriseServerUserAccountsUploadSyncState
Synchronization state of the Enterprise Server user accounts upload.
<h4>Valores</h4>
<p><strong>FAILURE</strong></p>
<p><p>The synchronization of the upload failed.</p></p>
<p><strong>PENDING</strong></p>
<p><p>The synchronization of the upload is pending.</p></p>
<p><strong>SUCCESS</strong></p>
<p><p>The synchronization of the upload succeeded.</p></p>
<h4>Valores</h4>
<p><strong>MEMBER</strong></p>
<p><p>The user is a member of the enterprise membership.</p></p>
<p><strong>OWNER</strong></p>
<p><p>The user is an owner of the enterprise membership.</p></p>
<h4>Valores</h4>
<p><strong>CLOUD</strong></p>
<p><p>The user is part of a GitHub Enterprise Cloud deployment.</p></p>
<p><strong>SERVER</strong></p>
<p><p>The user is part of a GitHub Enterprise Server deployment.</p></p>
<h4>Valores</h4>
<p><strong>DISMISSED</strong></p>
<p><p>The file has new changes since last viewed.</p></p>
<p><strong>UNVIEWED</strong></p>
<p><p>The file has not been marked as viewed.</p></p>
<p><strong>VIEWED</strong></p>
<p><p>The file has been marked as viewed.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order gists by creation time.</p></p>
<p><strong>PUSHED_AT</strong></p>
<p><p>Order gists by push time.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order gists by update time.</p></p>
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>Gists that are public and secret.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>Public.</p></p>
<p><strong>SECRET</strong></p>
<p><p>Secret.</p></p>
<h4>Valores</h4>
<p><strong>BAD_CERT</strong></p>
<p><p>The signing certificate or its chain could not be verified.</p></p>
<p><strong>BAD_EMAIL</strong></p>
<p><p>Invalid email used for signing.</p></p>
<p><strong>EXPIRED_KEY</strong></p>
<p><p>Signing key expired.</p></p>
<p><strong>GPGVERIFY_ERROR</strong></p>
<p><p>Internal error - the GPG verification service misbehaved.</p></p>
<p><strong>GPGVERIFY_UNAVAILABLE</strong></p>
<p><p>Internal error - the GPG verification service is unavailable at the moment.</p></p>
<p><strong>INVALID</strong></p>
<p><p>Invalid signature.</p></p>
<p><strong>MALFORMED_SIG</strong></p>
<p><p>Malformed signature.</p></p>
<p><strong>NOT_SIGNING_KEY</strong></p>
<p><p>The usage flags for the key that signed this don't allow signing.</p></p>
<p><strong>NO_USER</strong></p>
<p><p>Email used for signing not known to GitHub.</p></p>
<p><strong>OCSP_ERROR</strong></p>
<p><p>Valid signature, though certificate revocation check failed.</p></p>
<p><strong>OCSP_PENDING</strong></p>
<p><p>Valid signature, pending certificate revocation checking.</p></p>
<p><strong>OCSP_REVOKED</strong></p>
<p><p>One or more certificates in chain has been revoked.</p></p>
<p><strong>UNKNOWN_KEY</strong></p>
<p><p>Key used for signing not known to GitHub.</p></p>
<p><strong>UNKNOWN_SIG_TYPE</strong></p>
<p><p>Unknown signature type.</p></p>
<p><strong>UNSIGNED</strong></p>
<p><p>Unsigned.</p></p>
<p><strong>UNVERIFIED_EMAIL</strong></p>
<p><p>Email used for signing unverified on GitHub.</p></p>
<p><strong>VALID</strong></p>
<p><p>Valid signature and verified by GitHub.</p></p>
IdentityProviderConfigurationState
The possible states in which authentication can be configured with an identity provider.
<h4>Valores</h4>
<p><strong>CONFIGURED</strong></p>
<p><p>Authentication with an identity provider is configured but not enforced.</p></p>
<p><strong>ENFORCED</strong></p>
<p><p>Authentication with an identity provider is configured and enforced.</p></p>
<p><strong>UNCONFIGURED</strong></p>
<p><p>Authentication with an identity provider is not configured.</p></p>
<h4>Valores</h4>
<p><strong>DISABLED</strong></p>
<p><p>The setting is disabled for the owner.</p></p>
<p><strong>ENABLED</strong></p>
<p><p>The setting is enabled for the owner.</p></p>
<h4>Valores</h4>
<p><strong>ALLOW_LIST_VALUE</strong></p>
<p><p>Order IP allow list entries by the allow list value.</p></p>
<p><strong>CREATED_AT</strong></p>
<p><p>Order IP allow list entries by creation time.</p></p>
IpAllowListForInstalledAppsEnabledSettingValue
The possible values for the IP allow list configuration for installed GitHub Apps setting.
<h4>Valores</h4>
<p><strong>DISABLED</strong></p>
<p><p>The setting is disabled for the owner.</p></p>
<p><strong>ENABLED</strong></p>
<p><p>The setting is enabled for the owner.</p></p>
<h4>Valores</h4>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order issue comments by update time.</p></p>
<h4>Valores</h4>
<p><strong>COMMENTS</strong></p>
<p><p>Order issues by comment count.</p></p>
<p><strong>CREATED_AT</strong></p>
<p><p>Order issues by creation time.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order issues by update time.</p></p>
<h4>Valores</h4>
<p><strong>CLOSED</strong></p>
<p><p>An issue that has been closed.</p></p>
<p><strong>OPEN</strong></p>
<p><p>An issue that is still open.</p></p>
<h4>Valores</h4>
<p><strong>ADDED_TO_PROJECT_EVENT</strong></p>
<p><p>Represents a<code>added_to_project</code>event on a given issue or pull request.</p></p>
<p><strong>ASSIGNED_EVENT</strong></p>
<p><p>Represents an<code>assigned</code>event on any assignable object.</p></p>
<p><strong>CLOSED_EVENT</strong></p>
<p><p>Represents a<code>closed</code>event on any <code>Closable</code>.</p></p>
<p><strong>COMMENT_DELETED_EVENT</strong></p>
<p><p>Represents a<code>comment_deleted</code>event on a given issue or pull request.</p></p>
<p><strong>CONNECTED_EVENT</strong></p>
<p><p>Represents a<code>connected</code>event on a given issue or pull request.</p></p>
<p><strong>CONVERTED_NOTE_TO_ISSUE_EVENT</strong></p>
<p><p>Represents a<code>converted_note_to_issue</code>event on a given issue or pull request.</p></p>
<p><strong>CROSS_REFERENCED_EVENT</strong></p>
<p><p>Represents a mention made by one issue or pull request to another.</p></p>
<p><strong>DEMILESTONED_EVENT</strong></p>
<p><p>Represents a<code>demilestoned</code>event on a given issue or pull request.</p></p>
<p><strong>DISCONNECTED_EVENT</strong></p>
<p><p>Represents a<code>disconnected</code>event on a given issue or pull request.</p></p>
<p><strong>ISSUE_COMMENT</strong></p>
<p><p>Represents a comment on an Issue.</p></p>
<p><strong>LABELED_EVENT</strong></p>
<p><p>Represents a<code>labeled</code>event on a given issue or pull request.</p></p>
<p><strong>LOCKED_EVENT</strong></p>
<p><p>Represents a<code>locked</code>event on a given issue or pull request.</p></p>
<p><strong>MARKED_AS_DUPLICATE_EVENT</strong></p>
<p><p>Represents a<code>marked_as_duplicate</code>event on a given issue or pull request.</p></p>
<p><strong>MENTIONED_EVENT</strong></p>
<p><p>Represents a<code>mentioned</code>event on a given issue or pull request.</p></p>
<p><strong>MILESTONED_EVENT</strong></p>
<p><p>Represents a<code>milestoned</code>event on a given issue or pull request.</p></p>
<p><strong>MOVED_COLUMNS_IN_PROJECT_EVENT</strong></p>
<p><p>Represents a<code>moved_columns_in_project</code>event on a given issue or pull request.</p></p>
<p><strong>PINNED_EVENT</strong></p>
<p><p>Represents a<code>pinned</code>event on a given issue or pull request.</p></p>
<p><strong>REFERENCED_EVENT</strong></p>
<p><p>Represents a<code>referenced</code>event on a given <code>ReferencedSubject</code>.</p></p>
<p><strong>REMOVED_FROM_PROJECT_EVENT</strong></p>
<p><p>Represents a<code>removed_from_project</code>event on a given issue or pull request.</p></p>
<p><strong>RENAMED_TITLE_EVENT</strong></p>
<p><p>Represents a<code>renamed</code>event on a given issue or pull request.</p></p>
<p><strong>REOPENED_EVENT</strong></p>
<p><p>Represents a<code>reopened</code>event on any <code>Closable</code>.</p></p>
<p><strong>SUBSCRIBED_EVENT</strong></p>
<p><p>Represents a<code>subscribed</code>event on a given <code>Subscribable</code>.</p></p>
<p><strong>TRANSFERRED_EVENT</strong></p>
<p><p>Represents a<code>transferred</code>event on a given issue or pull request.</p></p>
<p><strong>UNASSIGNED_EVENT</strong></p>
<p><p>Represents an<code>unassigned</code>event on any assignable object.</p></p>
<p><strong>UNLABELED_EVENT</strong></p>
<p><p>Represents an<code>unlabeled</code>event on a given issue or pull request.</p></p>
<p><strong>UNLOCKED_EVENT</strong></p>
<p><p>Represents an<code>unlocked</code>event on a given issue or pull request.</p></p>
<p><strong>UNMARKED_AS_DUPLICATE_EVENT</strong></p>
<p><p>Represents an<code>unmarked_as_duplicate</code>event on a given issue or pull request.</p></p>
<p><strong>UNPINNED_EVENT</strong></p>
<p><p>Represents an<code>unpinned</code>event on a given issue or pull request.</p></p>
<p><strong>UNSUBSCRIBED_EVENT</strong></p>
<p><p>Represents an<code>unsubscribed</code>event on a given <code>Subscribable</code>.</p></p>
<p><strong>USER_BLOCKED_EVENT</strong></p>
<p><p>Represents a<code>user_blocked</code>event on a given user.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order labels by creation time.</p></p>
<p><strong>NAME</strong></p>
<p><p>Order labels by name.</p></p>
<h4>Valores</h4>
<p><strong>SIZE</strong></p>
<p><p>Order languages by the size of all files containing the language.</p></p>
<h4>Valores</h4>
<p><strong>OFF_TOPIC</strong></p>
<p><p>The issue or pull request was locked because the conversation was off-topic.</p></p>
<p><strong>RESOLVED</strong></p>
<p><p>The issue or pull request was locked because the conversation was resolved.</p></p>
<p><strong>SPAM</strong></p>
<p><p>The issue or pull request was locked because the conversation was spam.</p></p>
<p><strong>TOO_HEATED</strong></p>
<p><p>The issue or pull request was locked because the conversation was too heated.</p></p>
<h4>Valores</h4>
<p><strong>BEHIND</strong></p>
<p><p>The head ref is out of date.</p></p>
<p><strong>BLOCKED</strong></p>
<p><p>The merge is blocked.</p></p>
<p><strong>CLEAN</strong></p>
<p><p>Mergeable and passing commit status.</p></p>
<p><strong>DIRTY</strong></p>
<p><p>The merge commit cannot be cleanly created.</p></p>
<p><strong>DRAFT</strong></p>
<p><p>The merge is blocked due to the pull request being a draft.</p></p>
<p><strong>HAS_HOOKS</strong></p>
<p><p>Mergeable with passing commit status and pre-receive hooks.</p></p>
<p><strong>UNKNOWN</strong></p>
<p><p>The state cannot currently be determined.</p></p>
<p><strong>UNSTABLE</strong></p>
<p><p>Mergeable with non-passing commit status.</p></p>
<h4>Valores</h4>
<p><strong>CONFLICTING</strong></p>
<p><p>The pull request cannot be merged due to merge conflicts.</p></p>
<p><strong>MERGEABLE</strong></p>
<p><p>The pull request can be merged.</p></p>
<p><strong>UNKNOWN</strong></p>
<p><p>The mergeability of the pull request is still being calculated.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order milestones by when they were created.</p></p>
<p><strong>DUE_DATE</strong></p>
<p><p>Order milestones by when they are due.</p></p>
<p><strong>NUMBER</strong></p>
<p><p>Order milestones by their number.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order milestones by when they were last updated.</p></p>
<h4>Valores</h4>
<p><strong>CLOSED</strong></p>
<p><p>A milestone that has been closed.</p></p>
<p><strong>OPEN</strong></p>
<p><p>A milestone that is still open.</p></p>
<h4>Valores</h4>
<p><strong>ACTIVE</strong></p>
<p><p>The OAuth Application was active and allowed to have OAuth Accesses.</p></p>
<p><strong>PENDING_DELETION</strong></p>
<p><p>The OAuth Application was in the process of being deleted.</p></p>
<p><strong>SUSPENDED</strong></p>
<p><p>The OAuth Application was suspended from generating OAuth Accesses due to abuse or security concerns.</p></p>
<h4>Valores</h4>
<p><strong>ACCESS</strong></p>
<p><p>An existing resource was accessed.</p></p>
<p><strong>AUTHENTICATION</strong></p>
<p><p>A resource performed an authentication event.</p></p>
<p><strong>CREATE</strong></p>
<p><p>A new resource was created.</p></p>
<p><strong>MODIFY</strong></p>
<p><p>An existing resource was modified.</p></p>
<p><strong>REMOVE</strong></p>
<p><p>An existing resource was removed.</p></p>
<p><strong>RESTORE</strong></p>
<p><p>An existing resource was restored.</p></p>
<p><strong>TRANSFER</strong></p>
<p><p>An existing resource was transferred between multiple resources.</p></p>
OrderDirection
Possible directions in which to order a list of items when provided an orderBy argument.
<h4>Valores</h4>
<p><strong>ASC</strong></p>
<p><p>Specifies an ascending order for a given <code>orderBy</code> argument.</p></p>
<p><strong>DESC</strong></p>
<p><p>Specifies a descending order for a given <code>orderBy</code> argument.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Can read, clone, push, and add collaborators to repositories.</p></p>
<p><strong>READ</strong></p>
<p><p>Can read and clone repositories.</p></p>
<h4>Valores</h4>
<p><strong>BUSINESS</strong></p>
<p><p>Team Plan.</p></p>
<p><strong>BUSINESS_PLUS</strong></p>
<p><p>Enterprise Cloud Plan.</p></p>
<p><strong>FREE</strong></p>
<p><p>Free Plan.</p></p>
<p><strong>TIERED_PER_SEAT</strong></p>
<p><p>Tiered Per Seat Plan.</p></p>
<p><strong>UNLIMITED</strong></p>
<p><p>Legacy Unlimited Plan.</p></p>
OrgRemoveBillingManagerAuditEntryReason
The reason a billing manager was removed from an Organization.
<h4>Valores</h4>
<p><strong>SAML_EXTERNAL_IDENTITY_MISSING</strong></p>
<p><p>SAML external identity missing.</p></p>
<p><strong>SAML_SSO_ENFORCEMENT_REQUIRES_EXTERNAL_IDENTITY</strong></p>
<p><p>SAML SSO enforcement requires an external identity.</p></p>
<p><strong>TWO_FACTOR_REQUIREMENT_NON_COMPLIANCE</strong></p>
<p><p>The organization required 2FA of its billing managers and this user did not have 2FA enabled.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Organization administrators have full access and can change several settings,
including the names of repositories that belong to the Organization and Owners team membership. In addition, organization admins can delete the organization and all of its repositories.
<p><strong>BILLING_MANAGER</strong></p>
<p><p>A billing manager is a user who manages the billing settings for the Organization, such as updating payment information.</p></p>
<p><strong>DIRECT_MEMBER</strong></p>
<p><p>A direct member is a user that is a member of the Organization.</p></p>
<p><strong>OUTSIDE_COLLABORATOR</strong></p>
<p><p>An outside collaborator is a person who isn't explicitly a member of the
Organization, but who has Read, Write, or Admin permissions to one or more repositories in the organization.
<p><strong>UNAFFILIATED</strong></p>
<p><p>An unaffiliated collaborator is a person who is not a member of the
Organization and does not have access to any repositories in the Organization.
<h4>Valores</h4>
<p><strong>SAML_EXTERNAL_IDENTITY_MISSING</strong></p>
<p><p>SAML external identity missing.</p></p>
<p><strong>SAML_SSO_ENFORCEMENT_REQUIRES_EXTERNAL_IDENTITY</strong></p>
<p><p>SAML SSO enforcement requires an external identity.</p></p>
<p><strong>TWO_FACTOR_ACCOUNT_RECOVERY</strong></p>
<p><p>User was removed from organization during account recovery.</p></p>
<p><strong>TWO_FACTOR_REQUIREMENT_NON_COMPLIANCE</strong></p>
<p><p>The organization required 2FA of its billing managers and this user did not have 2FA enabled.</p></p>
<p><strong>USER_ACCOUNT_DELETED</strong></p>
<p><p>User account has been deleted.</p></p>
OrgRemoveOutsideCollaboratorAuditEntryMembershipType
The type of membership a user has with an Organization.
<h4>Valores</h4>
<p><strong>BILLING_MANAGER</strong></p>
<p><p>A billing manager is a user who manages the billing settings for the Organization, such as updating payment information.</p></p>
<p><strong>OUTSIDE_COLLABORATOR</strong></p>
<p><p>An outside collaborator is a person who isn't explicitly a member of the
Organization, but who has Read, Write, or Admin permissions to one or more repositories in the organization.
<p><strong>UNAFFILIATED</strong></p>
<p><p>An unaffiliated collaborator is a person who is not a member of the
Organization and does not have access to any repositories in the organization.
OrgRemoveOutsideCollaboratorAuditEntryReason
The reason an outside collaborator was removed from an Organization.
<h4>Valores</h4>
<p><strong>SAML_EXTERNAL_IDENTITY_MISSING</strong></p>
<p><p>SAML external identity missing.</p></p>
<p><strong>TWO_FACTOR_REQUIREMENT_NON_COMPLIANCE</strong></p>
<p><p>The organization required 2FA of its billing managers and this user did not have 2FA enabled.</p></p>
OrgUpdateDefaultRepositoryPermissionAuditEntryPermission
The default permission a repository can have in an Organization.
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Can read, clone, push, and add collaborators to repositories.</p></p>
<p><strong>NONE</strong></p>
<p><p>No default permission value.</p></p>
<p><strong>READ</strong></p>
<p><p>Can read and clone repositories.</p></p>
<p><strong>WRITE</strong></p>
<p><p>Can read, clone and push to repositories.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Can read, clone, push, and add collaborators to repositories.</p></p>
<p><strong>READ</strong></p>
<p><p>Can read and clone repositories.</p></p>
OrgUpdateMemberRepositoryCreationPermissionAuditEntryVisibility
The permissions available for repository creation on an Organization.
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>All organization members are restricted from creating any repositories.</p></p>
<p><strong>INTERNAL</strong></p>
<p><p>All organization members are restricted from creating internal repositories.</p></p>
<p><strong>NONE</strong></p>
<p><p>All organization members are allowed to create any repositories.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>All organization members are restricted from creating private repositories.</p></p>
<p><strong>PRIVATE_INTERNAL</strong></p>
<p><p>All organization members are restricted from creating private or internal repositories.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>All organization members are restricted from creating public repositories.</p></p>
<p><strong>PUBLIC_INTERNAL</strong></p>
<p><p>All organization members are restricted from creating public or internal repositories.</p></p>
<p><strong>PUBLIC_PRIVATE</strong></p>
<p><p>All organization members are restricted from creating public or private repositories.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>The user is invited to be an admin of the organization.</p></p>
<p><strong>BILLING_MANAGER</strong></p>
<p><p>The user is invited to be a billing manager of the organization.</p></p>
<p><strong>DIRECT_MEMBER</strong></p>
<p><p>The user is invited to be a direct member of the organization.</p></p>
<p><strong>REINSTATE</strong></p>
<p><p>The user's previous role will be reinstated.</p></p>
<h4>Valores</h4>
<p><strong>EMAIL</strong></p>
<p><p>The invitation was to an email address.</p></p>
<p><strong>USER</strong></p>
<p><p>The invitation was to an existing user.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>The user is an administrator of the organization.</p></p>
<p><strong>MEMBER</strong></p>
<p><p>The user is a member of the organization.</p></p>
OrganizationMembersCanCreateRepositoriesSettingValue
The possible values for the members can create repositories setting on an organization.
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>Members will be able to create public and private repositories.</p></p>
<p><strong>DISABLED</strong></p>
<p><p>Members will not be able to create public or private repositories.</p></p>
<p><strong>INTERNAL</strong></p>
<p><p>Members will be able to create only internal repositories.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>Members will be able to create only private repositories.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order organizations by creation time.</p></p>
<p><strong>LOGIN</strong></p>
<p><p>Order organizations by login.</p></p>
<h4>Valores</h4>
<p><strong>GIST</strong></p>
<p><p>A gist.</p></p>
<p><strong>ISSUE</strong></p>
<p><p>An issue.</p></p>
<p><strong>ORGANIZATION</strong></p>
<p><p>An organization.</p></p>
<p><strong>PROJECT</strong></p>
<p><p>A project.</p></p>
<p><strong>PULL_REQUEST</strong></p>
<p><p>A pull request.</p></p>
<p><strong>REPOSITORY</strong></p>
<p><p>A repository.</p></p>
<p><strong>TEAM</strong></p>
<p><p>A team.</p></p>
<p><strong>USER</strong></p>
<p><p>A user.</p></p>
PinnedDiscussionGradient
Preconfigured gradients that may be used to style discussions pinned within a repository.
<h4>Valores</h4>
<p><strong>BLUE_MINT</strong></p>
<p><p>A gradient of blue to mint.</p></p>
<p><strong>BLUE_PURPLE</strong></p>
<p><p>A gradient of blue to purple.</p></p>
<p><strong>PINK_BLUE</strong></p>
<p><p>A gradient of pink to blue.</p></p>
<p><strong>PURPLE_CORAL</strong></p>
<p><p>A gradient of purple to coral.</p></p>
<p><strong>RED_ORANGE</strong></p>
<p><p>A gradient of red to orange.</p></p>
PinnedDiscussionPattern
Preconfigured background patterns that may be used to style discussions pinned within a repository.
<h4>Valores</h4>
<p><strong>CHEVRON_UP</strong></p>
<p><p>An upward-facing chevron pattern.</p></p>
<p><strong>DOT</strong></p>
<p><p>A hollow dot pattern.</p></p>
<p><strong>DOT_FILL</strong></p>
<p><p>A solid dot pattern.</p></p>
<p><strong>HEART_FILL</strong></p>
<p><p>A heart pattern.</p></p>
<p><strong>PLUS</strong></p>
<p><p>A plus sign pattern.</p></p>
<p><strong>ZAP</strong></p>
<p><p>A lightning bolt pattern.</p></p>
<h4>Valores</h4>
<p><strong>ARCHIVED</strong></p>
<p><p>A project card that is archived.</p></p>
<p><strong>NOT_ARCHIVED</strong></p>
<p><p>A project card that is not archived.</p></p>
<h4>Valores</h4>
<p><strong>CONTENT_ONLY</strong></p>
<p><p>The card has content only.</p></p>
<p><strong>NOTE_ONLY</strong></p>
<p><p>The card has a note only.</p></p>
<p><strong>REDACTED</strong></p>
<p><p>The card is redacted.</p></p>
<h4>Valores</h4>
<p><strong>DONE</strong></p>
<p><p>The column contains cards which are complete.</p></p>
<p><strong>IN_PROGRESS</strong></p>
<p><p>The column contains cards which are currently being worked on.</p></p>
<p><strong>TODO</strong></p>
<p><p>The column contains cards still to be worked on.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order projects by creation time.</p></p>
<p><strong>NAME</strong></p>
<p><p>Order projects by name.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order projects by update time.</p></p>
<h4>Valores</h4>
<p><strong>CLOSED</strong></p>
<p><p>The project is closed.</p></p>
<p><strong>OPEN</strong></p>
<p><p>The project is open.</p></p>
<h4>Valores</h4>
<p><strong>AUTOMATED_KANBAN_V2</strong></p>
<p><p>Create a board with v2 triggers to automatically move cards across To do, In progress and Done columns.</p></p>
<p><strong>AUTOMATED_REVIEWS_KANBAN</strong></p>
<p><p>Create a board with triggers to automatically move cards across columns with review automation.</p></p>
<p><strong>BASIC_KANBAN</strong></p>
<p><p>Create a board with columns for To do, In progress and Done.</p></p>
<p><strong>BUG_TRIAGE</strong></p>
<p><p>Create a board to triage and prioritize bugs with To do, priority, and Done columns.</p></p>
<h4>Valores</h4>
<p><strong>MERGE</strong></p>
<p><p>Add all commits from the head branch to the base branch with a merge commit.</p></p>
<p><strong>REBASE</strong></p>
<p><p>Add all commits from the head branch onto the base branch individually.</p></p>
<p><strong>SQUASH</strong></p>
<p><p>Combine all commits from the head branch into a single commit in the base branch.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order pull_requests by creation time.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order pull_requests by update time.</p></p>
<h4>Valores</h4>
<p><strong>PENDING</strong></p>
<p><p>A comment that is part of a pending review.</p></p>
<p><strong>SUBMITTED</strong></p>
<p><p>A comment that is part of a submitted review.</p></p>
<h4>Valores</h4>
<p><strong>APPROVED</strong></p>
<p><p>The pull request has received an approving review.</p></p>
<p><strong>CHANGES_REQUESTED</strong></p>
<p><p>Changes have been requested on the pull request.</p></p>
<p><strong>REVIEW_REQUIRED</strong></p>
<p><p>A review is required before the pull request can be merged.</p></p>
<h4>Valores</h4>
<p><strong>APPROVE</strong></p>
<p><p>Submit feedback and approve merging these changes.</p></p>
<p><strong>COMMENT</strong></p>
<p><p>Submit general feedback without explicit approval.</p></p>
<p><strong>DISMISS</strong></p>
<p><p>Dismiss review so it now longer effects merging.</p></p>
<p><strong>REQUEST_CHANGES</strong></p>
<p><p>Submit feedback that must be addressed before merging.</p></p>
<h4>Valores</h4>
<p><strong>APPROVED</strong></p>
<p><p>A review allowing the pull request to merge.</p></p>
<p><strong>CHANGES_REQUESTED</strong></p>
<p><p>A review blocking the pull request from merging.</p></p>
<p><strong>COMMENTED</strong></p>
<p><p>An informational review.</p></p>
<p><strong>DISMISSED</strong></p>
<p><p>A review that has been dismissed.</p></p>
<p><strong>PENDING</strong></p>
<p><p>A review that has not yet been submitted.</p></p>
<h4>Valores</h4>
<p><strong>CLOSED</strong></p>
<p><p>A pull request that has been closed without being merged.</p></p>
<p><strong>MERGED</strong></p>
<p><p>A pull request that has been closed by being merged.</p></p>
<p><strong>OPEN</strong></p>
<p><p>A pull request that is still open.</p></p>
<h4>Valores</h4>
<p><strong>ADDED_TO_PROJECT_EVENT</strong></p>
<p><p>Represents a<code>added_to_project</code>event on a given issue or pull request.</p></p>
<p><strong>ASSIGNED_EVENT</strong></p>
<p><p>Represents an<code>assigned</code>event on any assignable object.</p></p>
<p><strong>AUTOMATIC_BASE_CHANGE_FAILED_EVENT</strong></p>
<p><p>Represents a<code>automatic_base_change_failed</code>event on a given pull request.</p></p>
<p><strong>AUTOMATIC_BASE_CHANGE_SUCCEEDED_EVENT</strong></p>
<p><p>Represents a<code>automatic_base_change_succeeded</code>event on a given pull request.</p></p>
<p><strong>AUTO_MERGE_DISABLED_EVENT</strong></p>
<p><p>Represents a<code>auto_merge_disabled</code>event on a given pull request.</p></p>
<p><strong>AUTO_MERGE_ENABLED_EVENT</strong></p>
<p><p>Represents a<code>auto_merge_enabled</code>event on a given pull request.</p></p>
<p><strong>AUTO_REBASE_ENABLED_EVENT</strong></p>
<p><p>Represents a<code>auto_rebase_enabled</code>event on a given pull request.</p></p>
<p><strong>AUTO_SQUASH_ENABLED_EVENT</strong></p>
<p><p>Represents a<code>auto_squash_enabled</code>event on a given pull request.</p></p>
<p><strong>BASE_REF_CHANGED_EVENT</strong></p>
<p><p>Represents a<code>base_ref_changed</code>event on a given issue or pull request.</p></p>
<p><strong>BASE_REF_DELETED_EVENT</strong></p>
<p><p>Represents a<code>base_ref_deleted</code>event on a given pull request.</p></p>
<p><strong>BASE_REF_FORCE_PUSHED_EVENT</strong></p>
<p><p>Represents a<code>base_ref_force_pushed</code>event on a given pull request.</p></p>
<p><strong>CLOSED_EVENT</strong></p>
<p><p>Represents a<code>closed</code>event on any <code>Closable</code>.</p></p>
<p><strong>COMMENT_DELETED_EVENT</strong></p>
<p><p>Represents a<code>comment_deleted</code>event on a given issue or pull request.</p></p>
<p><strong>CONNECTED_EVENT</strong></p>
<p><p>Represents a<code>connected</code>event on a given issue or pull request.</p></p>
<p><strong>CONVERTED_NOTE_TO_ISSUE_EVENT</strong></p>
<p><p>Represents a<code>converted_note_to_issue</code>event on a given issue or pull request.</p></p>
<p><strong>CONVERT_TO_DRAFT_EVENT</strong></p>
<p><p>Represents a<code>convert_to_draft</code>event on a given pull request.</p></p>
<p><strong>CROSS_REFERENCED_EVENT</strong></p>
<p><p>Represents a mention made by one issue or pull request to another.</p></p>
<p><strong>DEMILESTONED_EVENT</strong></p>
<p><p>Represents a<code>demilestoned</code>event on a given issue or pull request.</p></p>
<p><strong>DEPLOYED_EVENT</strong></p>
<p><p>Represents a<code>deployed</code>event on a given pull request.</p></p>
<p><strong>DEPLOYMENT_ENVIRONMENT_CHANGED_EVENT</strong></p>
<p><p>Represents a<code>deployment_environment_changed</code>event on a given pull request.</p></p>
<p><strong>DISCONNECTED_EVENT</strong></p>
<p><p>Represents a<code>disconnected</code>event on a given issue or pull request.</p></p>
<p><strong>HEAD_REF_DELETED_EVENT</strong></p>
<p><p>Represents a<code>head_ref_deleted</code>event on a given pull request.</p></p>
<p><strong>HEAD_REF_FORCE_PUSHED_EVENT</strong></p>
<p><p>Represents a<code>head_ref_force_pushed</code>event on a given pull request.</p></p>
<p><strong>HEAD_REF_RESTORED_EVENT</strong></p>
<p><p>Represents a<code>head_ref_restored</code>event on a given pull request.</p></p>
<p><strong>ISSUE_COMMENT</strong></p>
<p><p>Represents a comment on an Issue.</p></p>
<p><strong>LABELED_EVENT</strong></p>
<p><p>Represents a<code>labeled</code>event on a given issue or pull request.</p></p>
<p><strong>LOCKED_EVENT</strong></p>
<p><p>Represents a<code>locked</code>event on a given issue or pull request.</p></p>
<p><strong>MARKED_AS_DUPLICATE_EVENT</strong></p>
<p><p>Represents a<code>marked_as_duplicate</code>event on a given issue or pull request.</p></p>
<p><strong>MENTIONED_EVENT</strong></p>
<p><p>Represents a<code>mentioned</code>event on a given issue or pull request.</p></p>
<p><strong>MERGED_EVENT</strong></p>
<p><p>Represents a<code>merged</code>event on a given pull request.</p></p>
<p><strong>MILESTONED_EVENT</strong></p>
<p><p>Represents a<code>milestoned</code>event on a given issue or pull request.</p></p>
<p><strong>MOVED_COLUMNS_IN_PROJECT_EVENT</strong></p>
<p><p>Represents a<code>moved_columns_in_project</code>event on a given issue or pull request.</p></p>
<p><strong>PINNED_EVENT</strong></p>
<p><p>Represents a<code>pinned</code>event on a given issue or pull request.</p></p>
<p><strong>PULL_REQUEST_COMMIT</strong></p>
<p><p>Represents a Git commit part of a pull request.</p></p>
<p><strong>PULL_REQUEST_COMMIT_COMMENT_THREAD</strong></p>
<p><p>Represents a commit comment thread part of a pull request.</p></p>
<p><strong>PULL_REQUEST_REVIEW</strong></p>
<p><p>A review object for a given pull request.</p></p>
<p><strong>PULL_REQUEST_REVIEW_THREAD</strong></p>
<p><p>A threaded list of comments for a given pull request.</p></p>
<p><strong>PULL_REQUEST_REVISION_MARKER</strong></p>
<p><p>Represents the latest point in the pull request timeline for which the viewer has seen the pull request's commits.</p></p>
<p><strong>READY_FOR_REVIEW_EVENT</strong></p>
<p><p>Represents a<code>ready_for_review</code>event on a given pull request.</p></p>
<p><strong>REFERENCED_EVENT</strong></p>
<p><p>Represents a<code>referenced</code>event on a given <code>ReferencedSubject</code>.</p></p>
<p><strong>REMOVED_FROM_PROJECT_EVENT</strong></p>
<p><p>Represents a<code>removed_from_project</code>event on a given issue or pull request.</p></p>
<p><strong>RENAMED_TITLE_EVENT</strong></p>
<p><p>Represents a<code>renamed</code>event on a given issue or pull request.</p></p>
<p><strong>REOPENED_EVENT</strong></p>
<p><p>Represents a<code>reopened</code>event on any <code>Closable</code>.</p></p>
<p><strong>REVIEW_DISMISSED_EVENT</strong></p>
<p><p>Represents a<code>review_dismissed</code>event on a given issue or pull request.</p></p>
<p><strong>REVIEW_REQUESTED_EVENT</strong></p>
<p><p>Represents an<code>review_requested</code>event on a given pull request.</p></p>
<p><strong>REVIEW_REQUEST_REMOVED_EVENT</strong></p>
<p><p>Represents an<code>review_request_removed</code>event on a given pull request.</p></p>
<p><strong>SUBSCRIBED_EVENT</strong></p>
<p><p>Represents a<code>subscribed</code>event on a given <code>Subscribable</code>.</p></p>
<p><strong>TRANSFERRED_EVENT</strong></p>
<p><p>Represents a<code>transferred</code>event on a given issue or pull request.</p></p>
<p><strong>UNASSIGNED_EVENT</strong></p>
<p><p>Represents an<code>unassigned</code>event on any assignable object.</p></p>
<p><strong>UNLABELED_EVENT</strong></p>
<p><p>Represents an<code>unlabeled</code>event on a given issue or pull request.</p></p>
<p><strong>UNLOCKED_EVENT</strong></p>
<p><p>Represents an<code>unlocked</code>event on a given issue or pull request.</p></p>
<p><strong>UNMARKED_AS_DUPLICATE_EVENT</strong></p>
<p><p>Represents an<code>unmarked_as_duplicate</code>event on a given issue or pull request.</p></p>
<p><strong>UNPINNED_EVENT</strong></p>
<p><p>Represents an<code>unpinned</code>event on a given issue or pull request.</p></p>
<p><strong>UNSUBSCRIBED_EVENT</strong></p>
<p><p>Represents an<code>unsubscribed</code>event on a given <code>Subscribable</code>.</p></p>
<p><strong>USER_BLOCKED_EVENT</strong></p>
<p><p>Represents a<code>user_blocked</code>event on a given user.</p></p>
<h4>Valores</h4>
<p><strong>CLOSED</strong></p>
<p><p>A pull request that has been closed without being merged.</p></p>
<p><strong>OPEN</strong></p>
<p><p>A pull request that is still open.</p></p>
<h4>Valores</h4>
<p><strong>CONFUSED</strong></p>
<p><p>Represents the <code>:confused:</code> emoji.</p></p>
<p><strong>EYES</strong></p>
<p><p>Represents the <code>:eyes:</code> emoji.</p></p>
<p><strong>HEART</strong></p>
<p><p>Represents the <code>:heart:</code> emoji.</p></p>
<p><strong>HOORAY</strong></p>
<p><p>Represents the <code>:hooray:</code> emoji.</p></p>
<p><strong>LAUGH</strong></p>
<p><p>Represents the <code>:laugh:</code> emoji.</p></p>
<p><strong>ROCKET</strong></p>
<p><p>Represents the <code>:rocket:</code> emoji.</p></p>
<p><strong>THUMBS_DOWN</strong></p>
<p><p>Represents the <code>:-1:</code> emoji.</p></p>
<p><strong>THUMBS_UP</strong></p>
<p><p>Represents the <code>:+1:</code> emoji.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Allows ordering a list of reactions by when they were created.</p></p>
<h4>Valores</h4>
<p><strong>ALPHABETICAL</strong></p>
<p><p>Order refs by their alphanumeric name.</p></p>
<p><strong>TAG_COMMIT_DATE</strong></p>
<p><p>Order refs by underlying commit date if the ref prefix is refs/tags/.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order releases by creation time.</p></p>
<p><strong>NAME</strong></p>
<p><p>Order releases alphabetically by name.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
RepoChangeMergeSettingAuditEntryMergeType
The merge options available for pull requests to this repository.
<h4>Valores</h4>
<p><strong>MERGE</strong></p>
<p><p>The pull request is added to the base branch in a merge commit.</p></p>
<p><strong>REBASE</strong></p>
<p><p>Commits from the pull request are added onto the base branch individually without a merge commit.</p></p>
<p><strong>SQUASH</strong></p>
<p><p>The pull request's commits are squashed into a single commit before they are merged to the base branch.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
<h4>Valores</h4>
<p><strong>DUPLICATE</strong></p>
<p><p>A duplicated piece of content.</p></p>
<p><strong>OFF_TOPIC</strong></p>
<p><p>An irrelevant piece of content.</p></p>
<p><strong>OUTDATED</strong></p>
<p><p>An outdated piece of content.</p></p>
<p><strong>RESOLVED</strong></p>
<p><p>The content has been resolved.</p></p>
<h4>Valores</h4>
<p><strong>COLLABORATOR</strong></p>
<p><p>Repositories that the user has been added to as a collaborator.</p></p>
<p><strong>ORGANIZATION_MEMBER</strong></p>
<p><p>Repositories that the user has access to through being a member of an
organization. This includes every repository on every team that the user is on.
<p><strong>OWNER</strong></p>
<p><p>Repositories that are owned by the authenticated user.</p></p>
<h4>Valores</h4>
<p><strong>COMMIT</strong></p>
<p><p>Created a commit.</p></p>
<p><strong>ISSUE</strong></p>
<p><p>Created an issue.</p></p>
<p><strong>PULL_REQUEST</strong></p>
<p><p>Created a pull request.</p></p>
<p><strong>PULL_REQUEST_REVIEW</strong></p>
<p><p>Reviewed a pull request.</p></p>
<p><strong>REPOSITORY</strong></p>
<p><p>Created the repository.</p></p>
RepositoryInvitationOrderField
Properties by which repository invitation connections can be ordered.
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order repository invitations by creation time.</p></p>
<p><strong>INVITEE_LOGIN</strong></p>
<p><p>Order repository invitations by invitee login.</p></p>
<h4>Valores</h4>
<p><strong>BILLING</strong></p>
<p><p>The repository is locked due to a billing related reason.</p></p>
<p><strong>MIGRATING</strong></p>
<p><p>The repository is locked due to a migration.</p></p>
<p><strong>MOVING</strong></p>
<p><p>The repository is locked due to a move.</p></p>
<p><strong>RENAME</strong></p>
<p><p>The repository is locked due to a rename.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order repositories by creation time.</p></p>
<p><strong>NAME</strong></p>
<p><p>Order repositories by name.</p></p>
<p><strong>PUSHED_AT</strong></p>
<p><p>Order repositories by push time.</p></p>
<p><strong>STARGAZERS</strong></p>
<p><p>Order repositories by number of stargazers.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order repositories by update time.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>Can read, clone, and push to this repository. Can also manage issues, pull
requests, and repository settings, including adding collaborators.
<p><strong>MAINTAIN</strong></p>
<p><p>Can read, clone, and push to this repository. They can also manage issues, pull requests, and some repository settings.</p></p>
<p><strong>READ</strong></p>
<p><p>Can read and clone this repository. Can also open and comment on issues and pull requests.</p></p>
<p><strong>TRIAGE</strong></p>
<p><p>Can read and clone this repository. Can also manage issues and pull requests.</p></p>
<p><strong>WRITE</strong></p>
<p><p>Can read, clone, and push to this repository. Can also manage issues and pull requests.</p></p>
<h4>Valores</h4>
<p><strong>PRIVATE</strong></p>
<p><p>Private.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>Public.</p></p>
<h4>Valores</h4>
<p><strong>INTERNAL</strong></p>
<p><p>The repository is visible only to users in the same business.</p></p>
<p><strong>PRIVATE</strong></p>
<p><p>The repository is visible only to those with explicit access.</p></p>
<p><strong>PUBLIC</strong></p>
<p><p>The repository is visible to everyone.</p></p>
<h4>Valores</h4>
<p><strong>COMPLETED</strong></p>
<p><p>The check suite or run has been completed.</p></p>
<p><strong>IN_PROGRESS</strong></p>
<p><p>The check suite or run is in progress.</p></p>
<p><strong>PENDING</strong></p>
<p><p>The check suite or run is in pending state.</p></p>
<p><strong>QUEUED</strong></p>
<p><p>The check suite or run has been queued.</p></p>
<p><strong>WAITING</strong></p>
<p><p>The check suite or run is in waiting state.</p></p>
SamlDigestAlgorithm
The possible digest algorithms used to sign SAML requests for an identity provider.
<h4>Valores</h4>
<p><strong>SHA1</strong></p>
<p><p>SHA1.</p></p>
<p><strong>SHA256</strong></p>
<p><p>SHA256.</p></p>
<p><strong>SHA384</strong></p>
<p><p>SHA384.</p></p>
<p><strong>SHA512</strong></p>
<p><p>SHA512.</p></p>
SamlSignatureAlgorithm
The possible signature algorithms used to sign SAML requests for a Identity Provider.
<h4>Valores</h4>
<p><strong>RSA_SHA1</strong></p>
<p><p>RSA-SHA1.</p></p>
<p><strong>RSA_SHA256</strong></p>
<p><p>RSA-SHA256.</p></p>
<p><strong>RSA_SHA384</strong></p>
<p><p>RSA-SHA384.</p></p>
<p><strong>RSA_SHA512</strong></p>
<p><p>RSA-SHA512.</p></p>
<h4>Valores</h4>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order saved reply by when they were updated.</p></p>
<h4>Valores</h4>
<p><strong>DISCUSSION</strong></p>
<p><p>Returns matching discussions in repositories.</p></p>
<p><strong>ISSUE</strong></p>
<p><p>Returns results matching issues in repositories.</p></p>
<p><strong>REPOSITORY</strong></p>
<p><p>Returns results matching repositories.</p></p>
<p><strong>USER</strong></p>
<p><p>Returns results matching users and organizations on GitHub.</p></p>
<h4>Valores</h4>
<p><strong>COMPOSER</strong></p>
<p><p>PHP packages hosted at packagist.org.</p></p>
<p><strong>GO</strong></p>
<p><p>Go modules.</p></p>
<p><strong>MAVEN</strong></p>
<p><p>Java artifacts hosted at the Maven central repository.</p></p>
<p><strong>NPM</strong></p>
<p><p>JavaScript packages hosted at npmjs.com.</p></p>
<p><strong>NUGET</strong></p>
<p><p>.NET packages hosted at the NuGet Gallery.</p></p>
<p><strong>PIP</strong></p>
<p><p>Python packages hosted at PyPI.org.</p></p>
<p><strong>RUBYGEMS</strong></p>
<p><p>Ruby gems hosted at RubyGems.org.</p></p>
<h4>Valores</h4>
<p><strong>CRITICAL</strong></p>
<p><p>Critical.</p></p>
<p><strong>HIGH</strong></p>
<p><p>High.</p></p>
<p><strong>LOW</strong></p>
<p><p>Low.</p></p>
<p><strong>MODERATE</strong></p>
<p><p>Moderate.</p></p>
<h4>Valores</h4>
<p><strong>STARRED_AT</strong></p>
<p><p>Allows ordering a list of stars by when they were created.</p></p>
<h4>Valores</h4>
<p><strong>ERROR</strong></p>
<p><p>Status is errored.</p></p>
<p><strong>EXPECTED</strong></p>
<p><p>Status is expected.</p></p>
<p><strong>FAILURE</strong></p>
<p><p>Status is failing.</p></p>
<p><strong>PENDING</strong></p>
<p><p>Status is pending.</p></p>
<p><strong>SUCCESS</strong></p>
<p><p>Status is successful.</p></p>
<h4>Valores</h4>
<p><strong>IGNORED</strong></p>
<p><p>The User is never notified.</p></p>
<p><strong>SUBSCRIBED</strong></p>
<p><p>The User is notified of all conversations.</p></p>
<p><strong>UNSUBSCRIBED</strong></p>
<p><p>The User is only notified when participating or @mentioned.</p></p>
TeamDiscussionCommentOrderField
Properties by which team discussion comment connections can be ordered.
<h4>Valores</h4>
<p><strong>NUMBER</strong></p>
<p><p>Allows sequential ordering of team discussion comments (which is equivalent to chronological ordering).</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Allows chronological ordering of team discussions.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order team members by creation time.</p></p>
<p><strong>LOGIN</strong></p>
<p><p>Order team members by login.</p></p>
<h4>Valores</h4>
<p><strong>MAINTAINER</strong></p>
<p><p>A team maintainer has permission to add and remove team members.</p></p>
<p><strong>MEMBER</strong></p>
<p><p>A team member has no administrative permissions on the team.</p></p>
TeamMembershipType
Defines which types of team members are included in the returned list. Can be one of IMMEDIATE, CHILD_TEAM or ALL.
<h4>Valores</h4>
<p><strong>ALL</strong></p>
<p><p>Includes immediate and child team members for the team.</p></p>
<p><strong>CHILD_TEAM</strong></p>
<p><p>Includes only child team members for the team.</p></p>
<p><strong>IMMEDIATE</strong></p>
<p><p>Includes only immediate members of the team.</p></p>
<h4>Valores</h4>
<p><strong>NAME</strong></p>
<p><p>Allows ordering a list of teams by name.</p></p>
<h4>Valores</h4>
<p><strong>SECRET</strong></p>
<p><p>A secret team can only be seen by its members.</p></p>
<p><strong>VISIBLE</strong></p>
<p><p>A visible team can be seen and @mentioned by every member of the organization.</p></p>
<h4>Valores</h4>
<p><strong>CREATED_AT</strong></p>
<p><p>Order repositories by creation time.</p></p>
<p><strong>NAME</strong></p>
<p><p>Order repositories by name.</p></p>
<p><strong>PERMISSION</strong></p>
<p><p>Order repositories by permission.</p></p>
<p><strong>PUSHED_AT</strong></p>
<p><p>Order repositories by push time.</p></p>
<p><strong>STARGAZERS</strong></p>
<p><p>Order repositories by number of stargazers.</p></p>
<p><strong>UPDATED_AT</strong></p>
<p><p>Order repositories by update time.</p></p>
Aviso de pré-visualização
TeamReviewAssignmentAlgorithm is available under the Team review assignments preview. During the preview period, the API may change without notice.
<h4>Valores</h4>
<p><strong>LOAD_BALANCE</strong></p>
<p><p>Balance review load across the entire team.</p></p>
<p><strong>ROUND_ROBIN</strong></p>
<p><p>Alternate reviews between each team member.</p></p>
<h4>Valores</h4>
<p><strong>ADMIN</strong></p>
<p><p>User has admin rights on the team.</p></p>
<p><strong>MEMBER</strong></p>
<p><p>User is a member of the team.</p></p>
<h4>Valores</h4>
<p><strong>ONE_DAY</strong></p>
<p><p>The user was blocked for 1 day.</p></p>
<p><strong>ONE_MONTH</strong></p>
<p><p>The user was blocked for 30 days.</p></p>
<p><strong>ONE_WEEK</strong></p>
<p><p>The user was blocked for 7 days.</p></p>
<p><strong>PERMANENT</strong></p>
<p><p>The user was blocked permanently.</p></p>
<p><strong>THREE_DAYS</strong></p>
<p><p>The user was blocked for 3 days.</p></p>