-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GHES 3.12: Changes in generated code (#116)
* New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code * New updates to generated code
- Loading branch information
1 parent
ee360c0
commit 353d5af
Showing
43 changed files
with
445 additions
and
129 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,7 +34,7 @@ public Access_tokensRequestBuilder(string rawUrl, IRequestAdapter requestAdapter | |
{ | ||
} | ||
/// <summary> | ||
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.When using the repository or permission parameters to reduce the access of the token, the complexity of the token is increased due to both the number of permissions in the request and the number of repositories the token will have access to. If the complexity is too large, the token will fail to be issued. If this occurs, the error message will indicate the maximum number of repositories that should be requested. For the average application requesting 8 permissions, this limit is around 5000 repositories. With fewer permissions requested, more repositories are supported.You must use a [JWT](https://docs.github.com/[email protected]/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) to access this endpoint. | ||
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.You must use a [JWT](https://docs.github.com/[email protected]/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) to access this endpoint. | ||
/// API method documentation <see href="https://docs.github.com/[email protected]/rest/apps/apps#create-an-installation-access-token-for-an-app" /> | ||
/// </summary> | ||
/// <returns>A <see cref="global::GitHub.Models.InstallationToken"/></returns> | ||
|
@@ -66,7 +66,7 @@ public Access_tokensRequestBuilder(string rawUrl, IRequestAdapter requestAdapter | |
return await RequestAdapter.SendAsync<global::GitHub.Models.InstallationToken>(requestInfo, global::GitHub.Models.InstallationToken.CreateFromDiscriminatorValue, errorMapping, cancellationToken).ConfigureAwait(false); | ||
} | ||
/// <summary> | ||
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.When using the repository or permission parameters to reduce the access of the token, the complexity of the token is increased due to both the number of permissions in the request and the number of repositories the token will have access to. If the complexity is too large, the token will fail to be issued. If this occurs, the error message will indicate the maximum number of repositories that should be requested. For the average application requesting 8 permissions, this limit is around 5000 repositories. With fewer permissions requested, more repositories are supported.You must use a [JWT](https://docs.github.com/[email protected]/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) to access this endpoint. | ||
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.You must use a [JWT](https://docs.github.com/[email protected]/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) to access this endpoint. | ||
/// </summary> | ||
/// <returns>A <see cref="RequestInformation"/></returns> | ||
/// <param name="body">The request body</param> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -130,7 +130,7 @@ public partial class AlertsRequestBuilderGetQueryParameters | |
[QueryParameter("resolution")] | ||
public string Resolution { get; set; } | ||
#endif | ||
/// <summary>A comma-separated list of secret types to return. By default all secret types are returned.See "[Supported secret scanning patterns](https://docs.github.com/[email protected]/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)"for a complete list of secret types.</summary> | ||
/// <summary>A comma-separated list of secret types to return. By default all secret types are returned. See "[Supported secret scanning patterns](https://docs.github.com/[email protected]/enterprise-cloud@latest/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)" for a complete list of secret types.</summary> | ||
#if NETSTANDARD2_1_OR_GREATER || NETCOREAPP3_1_OR_GREATER | ||
#nullable enable | ||
[QueryParameter("secret_type")] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,8 +34,8 @@ public InitRequestBuilder(string rawUrl, IRequestAdapter requestAdapter) : base( | |
{ | ||
} | ||
/// <summary> | ||
/// When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// API method documentation <see href="https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload" /> | ||
/// When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.> [!IMPORTANT]> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// API method documentation <see href="https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-and-password" /> | ||
/// </summary> | ||
/// <param name="body">The request body</param> | ||
/// <param name="cancellationToken">Cancellation token to use when cancelling requests</param> | ||
|
@@ -54,7 +54,7 @@ public async Task PostAsync(global::GitHub.Models.GhesConfigInitRequest body, Ac | |
await RequestAdapter.SendNoContentAsync(requestInfo, default, cancellationToken).ConfigureAwait(false); | ||
} | ||
/// <summary> | ||
/// When you boot a GitHub instance for the first time, you can use this endpoint to upload a license.Note that you afterwards need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#start-configuration-apply-process) to start the actual configuration process.This endpoint also sets the root site administrator password which is used to authenticate with the GHES Manage API and the Management Console.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// When you boot and set up a GitHub instance for the first time, you can use this endpoint to upload a license and set the initial root site administrator password.> [!IMPORTANT]> To start the configuration process and apply the license, you need to `POST` to [`/manage/v1/config/apply`](https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#start-configuration-apply-process)The root site administrator password provided when calling this endpoint is used to authenticate for all other endpoints in the GHES Manage API and the Management Console UI.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// </summary> | ||
/// <returns>A <see cref="RequestInformation"/></returns> | ||
/// <param name="body">The request body</param> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -59,7 +59,7 @@ public LicenseRequestBuilder(string rawUrl, IRequestAdapter requestAdapter) : ba | |
return await RequestAdapter.SendAsync<global::GitHub.Models.GhesLicenseInfo>(requestInfo, global::GitHub.Models.GhesLicenseInfo.CreateFromDiscriminatorValue, default, cancellationToken).ConfigureAwait(false); | ||
} | ||
/// <summary> | ||
/// Uploads an enterprise license. This operation does not automatically activate the license.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// API method documentation <see href="https://docs.github.com/[email protected]/rest/enterprise-admin/manage-ghes#upload-an-enterprise-license" /> | ||
/// </summary> | ||
/// <returns>A List<global::GitHub.Models.GhesLicenseUpload></returns> | ||
|
@@ -100,7 +100,7 @@ public RequestInformation ToGetRequestInformation(Action<RequestConfiguration<De | |
return requestInfo; | ||
} | ||
/// <summary> | ||
/// Uploads an enterprise license. This operation does not automatically activate the license.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// Uploads a new enterprise license. In order to apply it right away, use the `apply` query parameter.> [!NOTE]> The request body for this operation must be submitted as `multipart/form-data` data. You can can reference the license file by prefixing the filename with the `@` symbol using `curl`. For more information, see the [`curl` documentation](https://curl.se/docs/manpage.html#-F). | ||
/// </summary> | ||
/// <returns>A <see cref="RequestInformation"/></returns> | ||
/// <param name="body">Binary request body</param> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.