Merge pull request #1656 from github/openapi-update-c79c769b41b3369c5576626d9cd6166e2c60f2e0ceefbed9c58322b7f78a3d93

Update OpenAPI 3.0 Descriptions

Author: dinonuggies1

descriptions/ghes-3.6/dereferenced/ghes-3.6.deref.json

@@ -333716,13 +333716,13 @@
       "post": {
         "summary": "Provision a SCIM enterprise group",
         "description": "**Note:** The SCIM API endpoints for enterprise accounts are currently in *private* beta and are subject to change.\n\nCreates a SCIM group for an enterprise.\n\nIf members are included as part of the group provisioning payload, they will be created as external group members. It is up to a provider to store a mapping between the `externalId` and `id` of each user.",
-        "operationId": "enterprise-admin/provision-and-invite-enterprise-group",
+        "operationId": "enterprise-admin/provision-enterprise-group",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group-and-invite-users"
+          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group"
         },
         "parameters": [
           {
@@ -336703,13 +336703,13 @@
       "post": {
         "summary": "Provision a SCIM enterprise user",
         "description": "**Note:** The SCIM API endpoints for enterprise accounts are currently in *private* beta and are subject to change.\n\nCreates an external identity for a new SCIM enterprise user.\n\nSCIM does not authenticate users, it only provisions them. The authentication of users is done by SAML. However, when SCIM is enabled, all users need to be provisioned through SCIM before a user can sign in through SAML. The matching of a user to a SCIM provisioned user is done when the SAML assertion is consumed. The user will be matched on SAML response `NameID` to SCIM `userName`.\n\nWhen converting existing enterprise to use SCIM, the user handle (`userName`) from the SCIM payload will be used to match the provisioned user to an already existing user in the enterprise. Since the new identity record is created for newly provisioned users the matching for those records is done using a user's handle. Currently the matching will be performed to all of the users no matter if they were SAML JIT provisioned or created as local users.",
-        "operationId": "enterprise-admin/provision-and-invite-enterprise-user",
+        "operationId": "enterprise-admin/provision-enterprise-user",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-and-invite-a-scim-enterprise-user"
+          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-user"
         },
         "parameters": [
           {

descriptions/ghes-3.6/dereferenced/ghes-3.6.deref.yaml

@@ -65370,12 +65370,12 @@ paths:
         Creates a SCIM group for an enterprise.
 
         If members are included as part of the group provisioning payload, they will be created as external group members. It is up to a provider to store a mapping between the `externalId` and `id` of each user.
-      operationId: enterprise-admin/provision-and-invite-enterprise-group
+      operationId: enterprise-admin/provision-enterprise-group
       tags:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group-and-invite-users
+        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group
       parameters:
       - *62
       requestBody:
@@ -65904,12 +65904,12 @@ paths:
         SCIM does not authenticate users, it only provisions them. The authentication of users is done by SAML. However, when SCIM is enabled, all users need to be provisioned through SCIM before a user can sign in through SAML. The matching of a user to a SCIM provisioned user is done when the SAML assertion is consumed. The user will be matched on SAML response `NameID` to SCIM `userName`.
 
         When converting existing enterprise to use SCIM, the user handle (`userName`) from the SCIM payload will be used to match the provisioned user to an already existing user in the enterprise. Since the new identity record is created for newly provisioned users the matching for those records is done using a user's handle. Currently the matching will be performed to all of the users no matter if they were SAML JIT provisioned or created as local users.
-      operationId: enterprise-admin/provision-and-invite-enterprise-user
+      operationId: enterprise-admin/provision-enterprise-user
       tags:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-and-invite-a-scim-enterprise-user
+        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-user
       parameters:
       - *62
       requestBody:

descriptions/ghes-3.6/ghes-3.6.json

@@ -44946,13 +44946,13 @@
       "post": {
         "summary": "Provision a SCIM enterprise group",
         "description": "**Note:** The SCIM API endpoints for enterprise accounts are currently in *private* beta and are subject to change.\n\nCreates a SCIM group for an enterprise.\n\nIf members are included as part of the group provisioning payload, they will be created as external group members. It is up to a provider to store a mapping between the `externalId` and `id` of each user.",
-        "operationId": "enterprise-admin/provision-and-invite-enterprise-group",
+        "operationId": "enterprise-admin/provision-enterprise-group",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group-and-invite-users"
+          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group"
         },
         "parameters": [
           {
@@ -45445,13 +45445,13 @@
       "post": {
         "summary": "Provision a SCIM enterprise user",
         "description": "**Note:** The SCIM API endpoints for enterprise accounts are currently in *private* beta and are subject to change.\n\nCreates an external identity for a new SCIM enterprise user.\n\nSCIM does not authenticate users, it only provisions them. The authentication of users is done by SAML. However, when SCIM is enabled, all users need to be provisioned through SCIM before a user can sign in through SAML. The matching of a user to a SCIM provisioned user is done when the SAML assertion is consumed. The user will be matched on SAML response `NameID` to SCIM `userName`.\n\nWhen converting existing enterprise to use SCIM, the user handle (`userName`) from the SCIM payload will be used to match the provisioned user to an already existing user in the enterprise. Since the new identity record is created for newly provisioned users the matching for those records is done using a user's handle. Currently the matching will be performed to all of the users no matter if they were SAML JIT provisioned or created as local users.",
-        "operationId": "enterprise-admin/provision-and-invite-enterprise-user",
+        "operationId": "enterprise-admin/provision-enterprise-user",
         "tags": [
           "enterprise-admin"
         ],
         "externalDocs": {
           "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-and-invite-a-scim-enterprise-user"
+          "url": "https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-user"
         },
         "parameters": [
           {

descriptions/ghes-3.6/ghes-3.6.yaml

@@ -32060,12 +32060,12 @@ paths:
         Creates a SCIM group for an enterprise.
 
         If members are included as part of the group provisioning payload, they will be created as external group members. It is up to a provider to store a mapping between the `externalId` and `id` of each user.
-      operationId: enterprise-admin/provision-and-invite-enterprise-group
+      operationId: enterprise-admin/provision-enterprise-group
       tags:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group-and-invite-users
+        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-group
       parameters:
       - "$ref": "#/components/parameters/enterprise"
       requestBody:
@@ -32408,12 +32408,12 @@ paths:
         SCIM does not authenticate users, it only provisions them. The authentication of users is done by SAML. However, when SCIM is enabled, all users need to be provisioned through SCIM before a user can sign in through SAML. The matching of a user to a SCIM provisioned user is done when the SAML assertion is consumed. The user will be matched on SAML response `NameID` to SCIM `userName`.
 
         When converting existing enterprise to use SCIM, the user handle (`userName`) from the SCIM payload will be used to match the provisioned user to an already existing user in the enterprise. Since the new identity record is created for newly provisioned users the matching for those records is done using a user's handle. Currently the matching will be performed to all of the users no matter if they were SAML JIT provisioned or created as local users.
-      operationId: enterprise-admin/provision-and-invite-enterprise-user
+      operationId: enterprise-admin/provision-enterprise-user
       tags:
       - enterprise-admin
       externalDocs:
         description: API method documentation
-        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-and-invite-a-scim-enterprise-user
+        url: https://docs.github.com/enterprise-server@3.6/rest/reference/enterprise-admin#provision-a-scim-enterprise-user
       parameters:
       - "$ref": "#/components/parameters/enterprise"
       requestBody: