Module types

Module types 

Source
Expand description

Data structures used by operation inputs/outputs.

Modules§

builders
Builders
error
Error types that AWS CodeCommit can respond with.

Structs§

Approval

Returns information about a specific approval on a pull request.

ApprovalRule

Returns information about an approval rule.

ApprovalRuleEventMetadata

Returns information about an event for an approval rule.

ApprovalRuleOverriddenEventMetadata

Returns information about an override event for approval rules for a pull request.

ApprovalRuleTemplate

Returns information about an approval rule template.

ApprovalStateChangedEventMetadata

Returns information about a change in the approval state for a pull request.

BatchAssociateApprovalRuleTemplateWithRepositoriesError

Returns information about errors in a BatchAssociateApprovalRuleTemplateWithRepositories operation.

BatchDescribeMergeConflictsError

Returns information about errors in a BatchDescribeMergeConflicts operation.

BatchDisassociateApprovalRuleTemplateFromRepositoriesError

Returns information about errors in a BatchDisassociateApprovalRuleTemplateFromRepositories operation.

BatchGetCommitsError

Returns information about errors in a BatchGetCommits operation.

BatchGetRepositoriesError

Returns information about errors in a BatchGetRepositories operation.

BlobMetadata

Returns information about a specific Git blob object.

BranchInfo

Returns information about a branch.

Comment

Returns information about a specific comment.

CommentsForComparedCommit

Returns information about comments on the comparison between two commits.

CommentsForPullRequest

Returns information about comments on a pull request.

Commit

Returns information about a specific commit.

Conflict

Information about conflicts in a merge operation.

ConflictMetadata

Information about the metadata for a conflict in a merge operation.

ConflictResolution

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

DeleteFileEntry

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.

FileMetadata

A file to be added, updated, or deleted as part of a commit.

FileModes

Information about file modes in a merge or pull request.

FileSizes

Information about the size of files in a merge or pull request.

FileVersion

Information about a version of a file.

Folder

Returns information about a folder in a repository.

IsBinaryFile

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.

MergeHunk

Information about merge hunks in a merge or pull request operation.

MergeHunkDetail

Information about the details of a merge hunk that contains a conflict in a merge or pull request operation.

MergeMetadata

Returns information about a merge or potential merge between a source reference and a destination reference in a pull request.

MergeOperations

Information about the file operation conflicts in a merge operation.

ObjectTypes

Information about the type of an object in a merge operation.

OriginApprovalRuleTemplate

Returns information about the template that created the approval rule for a pull request.

PullRequest

Returns information about a pull request.

PullRequestCreatedEventMetadata

Metadata about the pull request that is used when comparing the pull request source with its destination.

PullRequestEvent

Returns information about a pull request event.

PullRequestMergedStateChangedEventMetadata

Returns information about the change in the merge state for a pull request event.

PullRequestSourceReferenceUpdatedEventMetadata

Information about an update to the source branch of a pull request.

PullRequestStatusChangedEventMetadata

Information about a change to the status of a pull request.

PullRequestTarget

Returns information about a pull request target.

PutFileEntry

Information about a file added or updated as part of a commit.

ReactionForComment

Information about the reaction values provided by users on a comment.

ReactionValueFormats

Information about the values for reactions to a comment. CodeCommit supports a limited set of reactions.

ReplaceContentEntry

Information about a replacement content entry in the conflict of a merge or pull request operation.

RepositoryMetadata

Information about a repository.

RepositoryNameIdPair

Information about a repository name and ID.

RepositoryTrigger

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.

RepositoryTriggerExecutionFailure

A trigger failed to run.

SetFileModeEntry

Information about the file mode changes.

SourceFileSpecifier

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.

SymbolicLink

Returns information about a symbolic link in a repository folder.

Target

Returns information about a target for a pull request.

UserInfo

Information about the user who made a specified commit.

Enums§

ApprovalState
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.
BatchGetRepositoriesErrorCodeEnum
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.
ChangeTypeEnum
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.
ConflictDetailLevelTypeEnum
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.
ConflictResolutionStrategyTypeEnum
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.
FileModeTypeEnum
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.
MergeOptionTypeEnum
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.
ObjectTypeEnum
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.
OrderEnum
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.
OverrideStatus
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.
PullRequestEventType
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.
PullRequestStatusEnum
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.
RelativeFileVersionEnum
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.
ReplacementTypeEnum
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.
RepositoryTriggerEventEnum
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.
SortByEnum
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.