Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Approval
Returns information about a specific approval on a pull request.
- Approval
Rule Returns information about an approval rule.
- Approval
Rule Event Metadata Returns information about an event for an approval rule.
- Approval
Rule Overridden Event Metadata Returns information about an override event for approval rules for a pull request.
- Approval
Rule Template Returns information about an approval rule template.
- Approval
State Changed Event Metadata Returns information about a change in the approval state for a pull request.
- Batch
Associate Approval Rule Template With Repositories Error Returns information about errors in a BatchAssociateApprovalRuleTemplateWithRepositories operation.
- Batch
Describe Merge Conflicts Error Returns information about errors in a BatchDescribeMergeConflicts operation.
- Batch
Disassociate Approval Rule Template From Repositories Error Returns information about errors in a BatchDisassociateApprovalRuleTemplateFromRepositories operation.
- Batch
GetCommits Error Returns information about errors in a BatchGetCommits operation.
- Batch
GetRepositories Error Returns information about errors in a BatchGetRepositories operation.
- Blob
Metadata Returns information about a specific Git blob object.
- Branch
Info Returns information about a branch.
- Comment
Returns information about a specific comment.
- Comments
ForCompared Commit Returns information about comments on the comparison between two commits.
- Comments
ForPull Request Returns information about comments on a pull request.
- Commit
Returns information about a specific commit.
- Conflict
Information about conflicts in a merge operation.
- Conflict
Metadata Information about the metadata for a conflict in a merge operation.
- Conflict
Resolution If AUTOMERGE is the conflict resolution strategy, a list of inputs to use when resolving conflicts during a merge.
- Delete
File Entry A file that is deleted as part of a commit.
- Difference
Returns information about a set of differences for a commit specifier.
- Evaluation
Returns information about the approval rules applied to a pull request and whether conditions have been met.
- File
Returns information about a file in a repository.
- File
Metadata A file to be added, updated, or deleted as part of a commit.
- File
Modes Information about file modes in a merge or pull request.
- File
Sizes Information about the size of files in a merge or pull request.
- File
Version Information about a version of a file.
- Folder
Returns information about a folder in a repository.
- IsBinary
File Information about whether a file is binary or textual in a merge or pull request operation.
- Location
Returns information about the location of a change or comment in the comparison between two commits or a pull request.
- Merge
Hunk Information about merge hunks in a merge or pull request operation.
- Merge
Hunk Detail Information about the details of a merge hunk that contains a conflict in a merge or pull request operation.
- Merge
Metadata Returns information about a merge or potential merge between a source reference and a destination reference in a pull request.
- Merge
Operations Information about the file operation conflicts in a merge operation.
- Object
Types Information about the type of an object in a merge operation.
- Origin
Approval Rule Template Returns information about the template that created the approval rule for a pull request.
- Pull
Request Returns information about a pull request.
- Pull
Request Created Event Metadata Metadata about the pull request that is used when comparing the pull request source with its destination.
- Pull
Request Event Returns information about a pull request event.
- Pull
Request Merged State Changed Event Metadata Returns information about the change in the merge state for a pull request event.
- Pull
Request Source Reference Updated Event Metadata Information about an update to the source branch of a pull request.
- Pull
Request Status Changed Event Metadata Information about a change to the status of a pull request.
- Pull
Request Target Returns information about a pull request target.
- PutFile
Entry Information about a file added or updated as part of a commit.
- Reaction
ForComment Information about the reaction values provided by users on a comment.
- Reaction
Value Formats Information about the values for reactions to a comment. CodeCommit supports a limited set of reactions.
- Replace
Content Entry Information about a replacement content entry in the conflict of a merge or pull request operation.
- Repository
Metadata Information about a repository.
- Repository
Name IdPair Information about a repository name and ID.
- Repository
Trigger Information about a trigger for a repository.
If you want to receive notifications about repository events, consider using notifications instead of triggers. For more information, see Configuring notifications for repository events.
- Repository
Trigger Execution Failure A trigger failed to run.
- SetFile
Mode Entry Information about the file mode changes.
- Source
File Specifier Information about a source file that is part of changes made in a commit.
- SubModule
Returns information about a submodule reference in a repository folder.
- Symbolic
Link Returns information about a symbolic link in a repository folder.
- Target
Returns information about a target for a pull request.
- User
Info Information about the user who made a specified commit.
Enums§
- Approval
State - When writing a match expression against
ApprovalState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
GetRepositories Error Code Enum - When writing a match expression against
BatchGetRepositoriesErrorCodeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Change
Type Enum - When writing a match expression against
ChangeTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Conflict
Detail Level Type Enum - When writing a match expression against
ConflictDetailLevelTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Conflict
Resolution Strategy Type Enum - When writing a match expression against
ConflictResolutionStrategyTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - File
Mode Type Enum - When writing a match expression against
FileModeTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Merge
Option Type Enum - When writing a match expression against
MergeOptionTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Object
Type Enum - When writing a match expression against
ObjectTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Order
Enum - When writing a match expression against
OrderEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Override
Status - When writing a match expression against
OverrideStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Pull
Request Event Type - When writing a match expression against
PullRequestEventType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Pull
Request Status Enum - When writing a match expression against
PullRequestStatusEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Relative
File Version Enum - When writing a match expression against
RelativeFileVersionEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replacement
Type Enum - When writing a match expression against
ReplacementTypeEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Repository
Trigger Event Enum - When writing a match expression against
RepositoryTriggerEventEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Sort
ByEnum - When writing a match expression against
SortByEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.