See: newBatchDescribeMergeConflicts smart constructor.

Create a value of BatchDescribeMergeConflicts with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:filePaths:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_filePaths - The path of the target files used to describe the conflicts. If not specified, the default is all conflict files.

$sel:conflictDetailLevel:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_conflictDetailLevel - 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.

$sel:nextToken:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_nextToken - An enumeration token that, when provided in a request, returns the next batch of the results.

$sel:maxConflictFiles:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_maxConflictFiles - The maximum number of files to include in the output.

$sel:maxMergeHunks:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_maxMergeHunks - The maximum number of merge hunks to include in the output.

$sel:conflictResolutionStrategy:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_conflictResolutionStrategy - 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.

$sel:repositoryName:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_repositoryName - The name of the repository that contains the merge conflicts you want to review.

$sel:destinationCommitSpecifier:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_destinationCommitSpecifier - The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

$sel:sourceCommitSpecifier:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_sourceCommitSpecifier - The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

$sel:mergeOption:BatchDescribeMergeConflicts', batchDescribeMergeConflicts_mergeOption - The merge option or strategy you want to use to merge the 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.

See: newBatchDescribeMergeConflictsResponse smart constructor.

Create a value of BatchDescribeMergeConflictsResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:baseCommitId:BatchDescribeMergeConflictsResponse', batchDescribeMergeConflictsResponse_baseCommitId - The commit ID of the merge base.

$sel:nextToken:BatchDescribeMergeConflicts', batchDescribeMergeConflictsResponse_nextToken - An enumeration token that can be used in a request to return the next batch of the results.

$sel:errors:BatchDescribeMergeConflictsResponse', batchDescribeMergeConflictsResponse_errors - A list of any errors returned while describing the merge conflicts for each file.

$sel:httpStatus:BatchDescribeMergeConflictsResponse', batchDescribeMergeConflictsResponse_httpStatus - The response's http status code.

$sel:conflicts:BatchDescribeMergeConflictsResponse', batchDescribeMergeConflictsResponse_conflicts - A list of conflicts for each file, including the conflict metadata and the hunks of the differences between the files.

$sel:destinationCommitId:BatchDescribeMergeConflictsResponse', batchDescribeMergeConflictsResponse_destinationCommitId - The commit ID of the destination commit specifier that was used in the merge evaluation.

$sel:sourceCommitId:BatchDescribeMergeConflictsResponse', batchDescribeMergeConflictsResponse_sourceCommitId - The commit ID of the source commit specifier that was used in the merge evaluation.

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.