Repo sync

src/ghes-releases/lib/enterprise-dates.json

@@ -277,9 +277,9 @@
  },
  "3.22": {
  "releaseDate": "2026-08-11",
- "deprecationDate": "2027-09-01",
+ "deprecationDate": "2027-09-08",
  "releaseCandidateDate": "2026-08-11",
- "generalAvailabilityDate": "2026-09-01"
+ "generalAvailabilityDate": "2026-09-08"
  },
  "3.23": {
  "releaseDate": "2026-11-10",

src/graphql/data/ghes-3.21/schema-enterprise-admin.json

@@ -99,7 +99,7 @@
  "name": "createEnterpriseOrganization",
  "id": "createenterpriseorganization",
  "href": "/graphql/reference/enterprise-admin#mutation-createenterpriseorganization",
- "description": "<p>Creates an organization as part of an enterprise account. User-authenticated\nrequests make the viewer an owner and invite users in <code>adminLogins</code>.\nInstallation requests directly add listed enterprise members and invite other\nlisted users. Enterprise Managed User enterprises directly add managed users.\nInvitation failures do not roll back organization creation. A personal access\ntoken used to create an organization is implicitly permitted to update the\norganization it created, if the organization is part of an enterprise that has\nSAML enabled or uses Enterprise Managed Users. If the organization is not part\nof such an enterprise, and instead has SAML enabled for it individually, the\ntoken will then require SAML authorization to continue working against that organization.</p>",
+ "description": "<p>Creates an organization as part of an enterprise account. User-authenticated\nrequests make the viewer an owner. Users listed in <code>adminLogins</code> are invited\nas owners unless owner invitations are disabled, in which case they are added\ndirectly. Installation requests also add existing enterprise members directly.\nInvitation failures do not roll back organization creation. A personal access\ntoken used to create an organization is implicitly permitted to update the\norganization it created, if the organization is part of an enterprise that has\nSAML enabled or uses Enterprise Managed Users. If the organization is not part\nof such an enterprise, and instead has SAML enabled for it individually, the\ntoken will then require SAML authorization to continue working against that organization.</p>",
  "inputFields": [
  {
  "name": "input",
@@ -10163,7 +10163,7 @@
  "inputFields": [
  {
  "name": "adminLogins",
- "description": "<p>For user-authenticated requests, the logins of additional owners to invite.\nFor installation requests, existing enterprise members are added directly and\nother listed users are invited.</p>",
+ "description": "<p>The logins of additional organization owners. Listed users are invited unless\nowner invitations are disabled, in which case they are added directly.\nInstallation requests also add existing enterprise members directly.</p>",
  "type": "[String!]!",
  "id": "string",
  "href": "/graphql/reference/other#scalar-string"

src/graphql/data/ghes-3.21/schema.docs-enterprise.graphql

@@ -7812,9 +7812,9 @@ Autogenerated input type of CreateEnterpriseOrganization
 """
 input CreateEnterpriseOrganizationInput {
  """
-For user-authenticated requests, the logins of additional owners to invite.
-For installation requests, existing enterprise members are added directly and
-other listed users are invited.
+The logins of additional organization owners. Listed users are invited unless
+owner invitations are disabled, in which case they are added directly.
+Installation requests also add existing enterprise members directly.
  """
  adminLogins: [String!]!
 
@@ -24479,9 +24479,9 @@ type Mutation {
 
  """
  Creates an organization as part of an enterprise account. User-authenticated
- requests make the viewer an owner and invite users in `adminLogins`.
-Installation requests directly add listed enterprise members and invite other
-listed users. Enterprise Managed User enterprises directly add managed users.
+ requests make the viewer an owner. Users listed in `adminLogins` are invited
+as owners unless owner invitations are disabled, in which case they are added
+directly. Installation requests also add existing enterprise members directly.
  Invitation failures do not roll back organization creation. A personal access
  token used to create an organization is implicitly permitted to update the
  organization it created, if the organization is part of an enterprise that has

src/graphql/data/ghes-3.22/schema-enterprise-admin.json

@@ -154,7 +154,7 @@
  "name": "createEnterpriseOrganization",
  "id": "createenterpriseorganization",
  "href": "/graphql/reference/enterprise-admin#mutation-createenterpriseorganization",
- "description": "<p>Creates an organization as part of an enterprise account. User-authenticated\nrequests make the viewer an owner and invite users in <code>adminLogins</code>.\nInstallation requests directly add listed enterprise members and invite other\nlisted users. Enterprise Managed User enterprises directly add managed users.\nInvitation failures do not roll back organization creation. A personal access\ntoken used to create an organization is implicitly permitted to update the\norganization it created, if the organization is part of an enterprise that has\nSAML enabled or uses Enterprise Managed Users. If the organization is not part\nof such an enterprise, and instead has SAML enabled for it individually, the\ntoken will then require SAML authorization to continue working against that organization.</p>",
+ "description": "<p>Creates an organization as part of an enterprise account. User-authenticated\nrequests make the viewer an owner. Users listed in <code>adminLogins</code> are invited\nas owners unless owner invitations are disabled, in which case they are added\ndirectly. Installation requests also add existing enterprise members directly.\nInvitation failures do not roll back organization creation. A personal access\ntoken used to create an organization is implicitly permitted to update the\norganization it created, if the organization is part of an enterprise that has\nSAML enabled or uses Enterprise Managed Users. If the organization is not part\nof such an enterprise, and instead has SAML enabled for it individually, the\ntoken will then require SAML authorization to continue working against that organization.</p>",
  "isDeprecated": false,
  "inputFields": [
  {
@@ -10816,7 +10816,7 @@
  "inputFields": [
  {
  "name": "adminLogins",
- "description": "<p>For user-authenticated requests, the logins of additional owners to invite.\nFor installation requests, existing enterprise members are added directly and\nother listed users are invited.</p>",
+ "description": "<p>The logins of additional organization owners. Listed users are invited unless\nowner invitations are disabled, in which case they are added directly.\nInstallation requests also add existing enterprise members directly.</p>",
  "type": "[String!]!",
  "id": "string",
  "href": "/graphql/reference/other#scalar-string"

src/graphql/data/ghes-3.22/schema.docs-enterprise.graphql

@@ -7924,9 +7924,9 @@ Autogenerated input type of CreateEnterpriseOrganization
 """
 input CreateEnterpriseOrganizationInput {
  """
-For user-authenticated requests, the logins of additional owners to invite.
-For installation requests, existing enterprise members are added directly and
-other listed users are invited.
+The logins of additional organization owners. Listed users are invited unless
+owner invitations are disabled, in which case they are added directly.
+Installation requests also add existing enterprise members directly.
  """
  adminLogins: [String!]!
 
@@ -25326,9 +25326,9 @@ type Mutation @docsCategory(name: "meta") {
 
  """
  Creates an organization as part of an enterprise account. User-authenticated
- requests make the viewer an owner and invite users in `adminLogins`.
-Installation requests directly add listed enterprise members and invite other
-listed users. Enterprise Managed User enterprises directly add managed users.
+ requests make the viewer an owner. Users listed in `adminLogins` are invited
+as owners unless owner invitations are disabled, in which case they are added
+directly. Installation requests also add existing enterprise members directly.
  Invitation failures do not roll back organization creation. A personal access
  token used to create an organization is implicitly permitted to update the
  organization it created, if the organization is part of an enterprise that has