The full commit ID of the original or updated commit in the pull request source branch. Pass this value if you want an exception thrown if the current commit ID of the tip of the source branch does not match this commit ID.

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

The name of the repository where the pull request was created.

Information about the specified pull request, including the merge.

The response's http status code.

The current name of the repository.

The new name for the repository.

The location of the change where you want to post your comment. If no location is provided, the comment is posted as a general comment on the pull request difference between the before commit ID and the after commit ID.

A unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

The name of the repository where you want to post a comment on a pull request.

The full commit ID of the commit in the destination branch that was the tip of the branch at the time the pull request was created.

The full commit ID of the commit in the source branch that is the current tip of the branch for the pull request when you post the comment.

The content of your comment on the change.

In the directionality of the pull request, the blob ID of the before blob.

The location of the change where you posted your comment.

The full commit ID of the commit in the destination branch where the pull request is merged.

The system-generated ID of the pull request.

In the directionality of the pull request, the blob ID of the after blob.

The full commit ID of the commit in the source branch used to create the pull request, or in the case of an updated pull request, the full commit ID of the commit used to update the pull request.

The name of the repository where you posted a comment on a pull request.

The content of the comment you posted.

The response's http status code.

The email address of the person merging the branches. This information is used in the commit information for the merge.

The name of the author who created the commit. This information is used as both the author and committer for the commit.

The branch where the merge is applied.

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

The commit message for the merge.

If AUTOMERGE is the conflict resolution strategy, a list of inputs to use when resolving conflicts during a merge.

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If this is specified as true, a .gitkeep file is created for empty folders. The default is false.

The name of the repository where you want to merge two branches.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The commit ID of the merge in the destination or target branch.

The tree ID of the merge in the destination or target branch.

The response's http status code.

The name of the repository to which the commit was made.

The commit ID. Commit IDs are the full SHA ID of the commit.

The response's http status code.

A commit data type object that contains information about the specified commit.

The name of the template you want to associate with one or more repositories.

The names of the repositories you want to associate with the template.

The length constraint limit is for each string in the array. The array itself can be empty.

The response's http status code.

A list of names of the repositories that have been associated with the template.

A list of any errors that might have occurred while attempting to create the association between the template and the repositories.

An enumeration token that, when provided in a request, returns the next batch of the results.

Optional. The Amazon Resource Name (ARN) of the user or identity for which you want to get reaction information.

A non-zero, non-negative integer used to limit the number of returned results. The default is the same as the allowed maximum, 1,000.

The ID of the comment for which you want to get reactions information.

An enumeration token that can be used in a request to return the next batch of the results.

The response's http status code.

An array of reactions to the specified comment.

The name of the approval rule template for which you want to get information.

The response's http status code.

The content and structure of the approval rule template.

The name of the approval rule template to disassociate from a specified repository.

The name of the repository you want to disassociate from the template.

The name of the branch for which you want to retrieve information.

The name of the repository that contains the branch for which you want to retrieve information.

The name of the branch.

The response's http status code.

The file path in which to check differences. Limits the results to this path. Can also be used to specify the changed name of a directory or folder, if it has changed. If not specified, differences are shown for all paths.

An enumeration token that, when provided in a request, returns the next batch of the results.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, the full commit ID). Optional. If not specified, all changes before the afterCommitSpecifier value are shown. If you do not use beforeCommitSpecifier in your request, consider limiting the results with maxResults.

The file path in which to check for differences. Limits the results to this path. Can also be used to specify the previous name of a directory or folder. If beforePath and afterPath are not specified, differences are shown for all paths.

A non-zero, non-negative integer used to limit the number of returned results.

The name of the repository where you want to get differences.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit.

An enumeration token that can be used in a request to return the next batch of the results.

A data type object that contains information about the differences, including whether the difference is added, modified, or deleted (A, D, M).

The response's http status code.

An enumeration token that, when provided in a request, returns the next batch of the results.

The Amazon Resource Name (ARN) of the resource for which you want to get information about tags, if any.

An enumeration token that allows the operation to batch the next results of the operation.

A list of tag key and value pairs associated with the specified resource.

The response's http status code.

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

The response's http status code.

Information about the specified pull request.

The system-generated ID of the pull request for which you want to override all approval rule requirements. To get this information, use GetPullRequest.

The system-generated ID of the most recent revision of the pull request. You cannot override approval rules for anything but the most recent revision of a pull request. To get the revision ID, use GetPullRequest.

Whether you want to set aside approval rule requirements for the pull request (OVERRIDE) or revoke a previous override and apply approval rule requirements (REVOKE). REVOKE status is not stored.

Optional. The Amazon Resource Name (ARN) of the user who created the pull request. If used, this filters the results to pull requests created by that user.

An enumeration token that, when provided in a request, returns the next batch of the results.

Optional. The status of the pull request. If used, this refines the results to the pull requests that match the specified status.

A non-zero, non-negative integer used to limit the number of returned results.

The name of the repository for which you want to list pull requests.

An enumeration token that allows the operation to batch the next results of the operation.

The response's http status code.

The system-generated IDs of the pull requests.

The file modes to update for files in this commit.

The email address of the person who created the commit.

The name of the author who created the commit. This information is used as both the author and committer for the commit.

The ID of the commit that is the parent of the commit you create. Not required if this is an empty repository.

The files to delete in this commit. These files still exist in earlier commits.

The files to add or update in this commit.

The commit message you want to include in the commit. Commit messages are limited to 256 KB. If no message is specified, a default message is used.

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If true, a ..gitkeep file is created for empty folders. The default is false.

The name of the repository where you create the commit.

The name of the branch where you create the commit.

The full commit ID of the commit that contains your committed file changes.

The full SHA-1 pointer of the tree information for the commit that contains the commited file changes.

The files added as part of the committed file changes.

The files updated as part of the commited file changes.

The files deleted as part of the committed file changes.

The response's http status code.

The system-generated ID of the pull request.

The system-generated ID of the revision.

The approval state to associate with the user on the pull request.

The system-generated ID of the pull request you want to evaluate.

The system-generated ID for the pull request revision. To retrieve the most recent revision ID for a pull request, use GetPullRequest.

The response's http status code.

The result of the evaluation, including the names of the rules whose conditions have been met (if any), the names of the rules whose conditions have not been met (if any), whether the pull request is in the approved state, and whether the pull request approval rule has been set aside by an override.

The unique, system-generated ID of the comment. To get this ID, use GetCommentsForComparedCommit or GetCommentsForPullRequest.

The contents of the comment.

The response's http status code.

The description of the approval rule template. Consider providing a description that explains what this template does and when it might be appropriate to associate it with repositories.

The name of the approval rule template. Provide descriptive names, because this name is applied to the approval rules created automatically in associated repositories.

The content of the approval rule that is created on pull requests in associated repositories. If you specify one or more destination references (branches), approval rules are created in an associated repository only if their destination references (branches) match those specified in the template.

When you create the content of the approval rule template, you can specify approvers in an approval pool in one of two ways:

• CodeCommitApprovers: This option only requires an AWS account and a resource. It can be used for both IAM users and federated access users whose name matches the provided resource name. This is a very powerful option that offers a great deal of flexibility. For example, if you specify the AWS account 123456789012 and Mary_Major, all of the following are counted as approvals coming from that user:

  • An IAM user in the account (arn:aws:iam::123456789012:user/Mary_Major)
  • A federated user identified in IAM as Mary_Major (arn:aws:sts::123456789012:federated-user/Mary_Major)

  This option does not recognize an active session of someone assuming the role of CodeCommitReview with a role session name of Mary_Major (arn:aws:sts::123456789012:assumed-role/CodeCommitReview/Mary_Major) unless you include a wildcard (*Mary_Major).

• Fully qualified ARN: This option allows you to specify the fully qualified Amazon Resource Name (ARN) of the IAM user or role.

For more information about IAM ARNs, wildcards, and formats, see IAM Identifiers in the IAM User Guide.

The response's http status code.

The content and structure of the created approval rule template.

The name of the repository that contains the branch to be deleted.

The name of the branch to delete.

Information about the branch deleted by the operation, including the branch name and the commit ID that was the tip of the branch.

The response's http status code.

The new comment or description for the specified repository. Repository descriptions are limited to 1,000 characters.

The name of the repository to set or change the comment or description for.

The name of the repository in which you want to create the new branch.

The name of the new branch to create.

The ID of the commit to point the new branch to.

A fully qualified reference used to identify a commit that contains the version of the folder's content to return. A fully qualified reference can be a commit ID, branch name, tag, or reference such as HEAD. If no specifier is provided, the folder content is returned as it exists in the HEAD commit.

The name of the repository.

The fully qualified path to the folder whose contents are returned, including the folder name. For example, /examples is a fully-qualified path to a folder named examples that was created off of the root directory (/) of a repository.

The list of submodules in the specified folder, if any.

The full SHA-1 pointer of the tree information for the commit that contains the folder.

The list of folders that exist under the specified folder, if any.

The list of symbolic links to other files and folders in the specified folder, if any.

The list of files in the specified folder, if any.

The response's http status code.

The full commit ID used as a reference for the returned version of the folder content.

The fully qualified path of the folder whose contents are returned.

A unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.

The AWS SDKs prepopulate client request tokens. If you are using an AWS SDK, an idempotency token is created for you.

A description of the pull request.

The title of the pull request. This title is used to identify the pull request to other users in the repository.

The targets for the pull request, including the source of the code to be reviewed (the source branch) and the destination where the creator of the pull request intends the code to be merged after the pull request is closed (the destination branch).

The response's http status code.

Information about the newly created pull request.

The name of the approval rule template to delete.

The response's http status code.

The system-generated ID of the deleted approval rule template. If the template has been previously deleted, the only response is a 200 OK.

An enumeration token that allows the operation to batch the results.

The name of the repository that contains the branches.

The list of branch names.

An enumeration token that returns the batch of the results.

The response's http status code.

The full commit IDs of the commits to get information about.

You must supply the full SHA IDs of each commit. You cannot use shortened SHA IDs.

The name of the repository that contains the commits.

An array of commit data type objects, each of which contains information about a specified commit.

Returns any commit IDs for which information could not be found. For example, if one of the commit IDs was a shortened SHA ID or that commit was not found in the specified repository, the ID returns an error object with more information.

The response's http status code.

The ID of the comment to which you want to add or update a reaction.

The emoji reaction you want to add or update. To remove a reaction, provide a value of blank or null. You can also provide the value of none. For information about emoji reaction values supported in AWS CodeCommit, see the AWS CodeCommit User Guide.

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

The updated content of the description for the pull request. This content replaces the existing description.

The response's http status code.

Information about the updated pull request.

An enumeration token that allows the operation to batch the results of the operation. Batch sizes are 1,000 for list repository operations. When the client sends the token back to AWS CodeCommit, another page of 1,000 records is retrieved.

The order in which to sort the results of a list repositories operation.

The criteria used to sort the results of a list repositories operation.

Lists the repositories called by the list repositories operation.

An enumeration token that allows the operation to batch the results of the operation. Batch sizes are 1,000 for list repository operations. When the client sends the token back to AWS CodeCommit, another page of 1,000 records is retrieved.

The response's http status code.

A comment or description about the new repository.

The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.

One or more tag key-value pairs to use when tagging this repository.

The name of the new repository to be created.

The repository name must be unique across the calling AWS account. Repository names are limited to 100 alphanumeric, dash, and underscore characters, and cannot include certain characters. For more information about the limits on repository names, see Limits in the AWS CodeCommit User Guide. The suffix .git is prohibited.

Information about the newly created repository.

The response's http status code.

The name of the repository to set or change the default branch for.

The name of the branch to set as the default.

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

The name of the repository that contains the commits about which you want to get merge options.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The response's http status code.

The merge option or strategy used to merge the code.

The commit ID of the source commit specifier that was used in the merge evaluation.

The commit ID of the destination commit specifier that was used in the merge evaluation.

The commit ID of the merge base.

The system-generated ID of the pull request for which you want to create the approval rule.

The name for the approval rule.

The content of the approval rule, including the number of approvals needed and the structure of an approval pool defined for approvals, if any. For more information about approval pools, see the AWS CodeCommit User Guide.

When you create the content of the approval rule, you can specify approvers in an approval pool in one of two ways:

• CodeCommitApprovers: This option only requires an AWS account and a resource. It can be used for both IAM users and federated access users whose name matches the provided resource name. This is a very powerful option that offers a great deal of flexibility. For example, if you specify the AWS account 123456789012 and Mary_Major, all of the following would be counted as approvals coming from that user:

  • An IAM user in the account (arn:aws:iam::123456789012:user/Mary_Major)
  • A federated user identified in IAM as Mary_Major (arn:aws:sts::123456789012:federated-user/Mary_Major)

  This option does not recognize an active session of someone assuming the role of CodeCommitReview with a role session name of Mary_Major (arn:aws:sts::123456789012:assumed-role/CodeCommitReview/Mary_Major) unless you include a wildcard (*Mary_Major).

• Fully qualified ARN: This option allows you to specify the fully qualified Amazon Resource Name (ARN) of the IAM user or role.

For more information about IAM ARNs, wildcards, and formats, see IAM Identifiers in the IAM User Guide.

The response's http status code.

Information about the created approval rule.

A unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.

The system-generated ID of the comment to which you want to reply. To get this ID, use GetCommentsForComparedCommit or GetCommentsForPullRequest.

The contents of your reply to a comment.

Information about the reply to a comment.

The response's http status code.

The SHA-256 hash signature for the content of the approval rule. You can retrieve this information by using GetPullRequest.

The name of the approval rule template where you want to update the content of the rule.

The content that replaces the existing content of the rule. Content statements must be complete. You cannot provide only the changes.

The response's http status code.

Undocumented member.

The email address for the person who created the unreferenced commit.

The name of the author who created the unreferenced commit. This information is used as both the author and committer for the commit.

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

The commit message for the unreferenced commit.

If AUTOMERGE is the conflict resolution strategy, a list of inputs to use when resolving conflicts during a merge.

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If this is specified as true, a .gitkeep file is created for empty folders. The default is false.

The name of the repository where you want to create the unreferenced merge commit.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The merge option or strategy you want to use to merge the code.

The full commit ID of the commit that contains your merge results.

The full SHA-1 pointer of the tree information for the commit that contains the merge results.

The response's http status code.

An enumeration token that, when provided in a request, returns the next batch of the results.

A non-zero, non-negative integer used to limit the number of returned results.

The name of the approval rule template for which you want to list repositories that are associated with that template.

A list of repository names that are associated with the specified approval rule template.

An enumeration token that allows the operation to batch the next results of the operation.

The response's http status code.

The name of the repository to get information about.

Information about the repository.

The response's http status code.

The path of the target files used to describe the conflicts. If not specified, the default is all conflict files.

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

An enumeration token that, when provided in a request, returns the next batch of the results.

The maximum number of files to include in the output.

The maximum number of merge hunks to include in the output.

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

The name of the repository that contains the merge conflicts you want to review.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The merge option or strategy you want to use to merge the code.

The commit ID of the merge base.

An enumeration token that can be used in a request to return the next batch of the results.

A list of any errors returned while describing the merge conflicts for each file.

The response's http status code.

A list of conflicts for each file, including the conflict metadata and the hunks of the differences between the files.

The commit ID of the destination commit specifier that was used in the merge evaluation.

The commit ID of the source commit specifier that was used in the merge evaluation.

The system-generated ID of the pull request that contains the approval rule you want to delete.

The name of the approval rule you want to delete.

The response's http status code.

The ID of the deleted approval rule.

If the approval rule was deleted in an earlier API call, the response is 200 OK without content.

The name of the repository for which the trigger is configured.

The system-generated unique ID for the trigger.

The JSON block of configuration information for each trigger.

The response's http status code.

The current name of the approval rule template.

The new name you want to apply to the approval rule template.

The response's http status code.

The structure and content of the updated approval rule template.

An email address for the person adding or updating the file.

The file mode permissions of the blob. Valid file mode permissions are listed here.

The full commit ID of the head commit in the branch where you want to add or update the file. If this is an empty repository, no commit ID is required. If this is not an empty repository, a commit ID is required.

The commit ID must match the ID of the head commit at the time of the operation. Otherwise, an error occurs, and the file is not added or updated.

The name of the person adding or updating the file. Although it is optional, a name makes the commit history for your repository more useful.

A message about why this file was added or updated. Although it is optional, a message makes the commit history for your repository more useful.

The name of the repository where you want to add or update the file.

The name of the branch where you want to add or update the file. If this is an empty repository, this branch is created.

The content of the file, in binary object format.-- -- Note: This Lens automatically encodes and decodes Base64 data. -- The underlying isomorphism will encode to Base64 representation during -- serialisation, and decode from Base64 representation during deserialisation. -- This Lens accepts and returns only raw unencoded data.

The name of the file you want to add or update, including the relative path to the file in the repository.

If the path does not currently exist in the repository, the path is created as part of adding the file.

The response's http status code.

The full SHA ID of the commit that contains this file change.

The ID of the blob, which is its SHA-1 pointer.

The full SHA-1 pointer of the tree information for the commit that contains this file change.

The email address for the commit that deletes the file. If no email address is specified, the email address is left blank.

The name of the author of the commit that deletes the file. If no name is specified, the user's ARN is used as the author name and committer name.

The commit message you want to include as part of deleting the file. Commit messages are limited to 256 KB. If no message is specified, a default message is used.

If a file is the only object in the folder or directory, specifies whether to delete the folder or directory that contains the file. By default, empty folders are deleted. This includes empty folders that are part of the directory structure. For example, if the path to a file is dir1/dir2/dir3/dir4, and dir2 and dir3 are empty, deleting the last file in dir4 also deletes the empty folders dir4, dir3, and dir2.

The name of the repository that contains the file to delete.

The name of the branch where the commit that deletes the file is made.

The fully qualified path to the file that to be deleted, including the full name and extension of that file. For example, /examples/file.md is a fully qualified path to a file named file.md in a folder named examples.

The ID of the commit that is the tip of the branch where you want to create the commit that deletes the file. This must be the HEAD commit for the branch. The commit that deletes the file is created from this commit ID.

The response's http status code.

The full commit ID of the commit that contains the change that deletes the file.

The blob ID removed from the tree as part of deleting the file.

The full SHA-1 pointer of the tree information for the commit that contains the delete file change.

The fully qualified path to the file to be deleted, including the full name and extension of that file.

An enumeration token that when provided in a request, returns the next batch of the results.

To establish the directionality of the comparison, the full commit ID of the before commit.

A non-zero, non-negative integer used to limit the number of returned results. The default is 100 comments, but you can configure up to 500.

The name of the repository where you want to compare commits.

To establish the directionality of the comparison, the full commit ID of the after commit.

A list of comment objects on the compared commit.

An enumeration token that can be used in a request to return the next batch of the results.

The response's http status code.

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

The name of the repository that contains the merge commit about which you want to get information.

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

The commit ID for the merge commit created when the source branch was merged into the destination branch. If the fast-forward merge strategy was used, there is no merge commit.

The commit ID of the destination commit specifier that was used in the merge evaluation.

The commit ID of the merge base.

The commit ID of the source commit specifier that was used in the merge evaluation.

The response's http status code.

The name of the repository in which to test the triggers.

The list of triggers to test.

The list of triggers that were not tested. This list provides the names of the triggers that could not be tested, separated by commas.

The list of triggers that were successfully tested. This list provides the names of the triggers that were successfully tested, separated by commas.

The response's http status code.

The email address of the person merging the branches. This information is used in the commit information for the merge.

The name of the author who created the commit. This information is used as both the author and committer for the commit.

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

The commit message to include in the commit information for the merge.

If AUTOMERGE is the conflict resolution strategy, a list of inputs to use when resolving conflicts during a merge.

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If true, a .gitkeep file is created for empty folders. The default is false.

The full commit ID of the original or updated commit in the pull request source branch. Pass this value if you want an exception thrown if the current commit ID of the tip of the source branch does not match this commit ID.

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

The name of the repository where the pull request was created.

Undocumented member.

The response's http status code.

The system-generated ID of the comment you want to update. To get this ID, use GetCommentsForComparedCommit or GetCommentsForPullRequest.

The updated content to replace the existing content of the comment.

Information about the updated comment.

The response's http status code.

The location of the comparison where you want to comment.

To establish the directionality of the comparison, the full commit ID of the before commit. Required for commenting on any commit unless that commit is the initial commit.

A unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.

The name of the repository where you want to post a comment on the comparison between commits.

To establish the directionality of the comparison, the full commit ID of the after commit.

The content of the comment you want to make.

In the directionality you established, the blob ID of the before blob.

The location of the comment in the comparison between the two commits.