Returns information about merge conflicts between the before and after commit IDs for a pull request in a repository
Source:R/codecommit_operations.R
codecommit_get_merge_conflicts.RdReturns information about merge conflicts between the before and after commit IDs for a pull request in a repository.
See https://www.paws-r-sdk.com/docs/codecommit_get_merge_conflicts/ for full documentation.
Usage
codecommit_get_merge_conflicts(
repositoryName,
destinationCommitSpecifier,
sourceCommitSpecifier,
mergeOption,
conflictDetailLevel = NULL,
maxConflictFiles = NULL,
conflictResolutionStrategy = NULL,
nextToken = NULL
)Arguments
- repositoryName
[required] The name of the repository where the pull request was created.
- destinationCommitSpecifier
[required] The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).
- sourceCommitSpecifier
[required] The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).
- mergeOption
[required] The merge option or strategy you want to use to merge the code.
- 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.
- maxConflictFiles
The maximum number of files to include in the output.
- 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.
- nextToken
An enumeration token that, when provided in a request, returns the next batch of the results.