codecommit_create_unreferenced_merge_commit: Creates an unreferenced commit that represents the result of...

View source: R/codecommit_operations.R

codecommit_create_unreferenced_merge_commitR Documentation

Creates an unreferenced commit that represents the result of merging two branches using a specified merge strategy

Description

Creates an unreferenced commit that represents the result of merging two branches using a specified merge strategy. This can help you determine the outcome of a potential merge. This API cannot be used with the fast-forward merge strategy because that strategy does not create a merge commit.

See https://www.paws-r-sdk.com/docs/codecommit_create_unreferenced_merge_commit/ for full documentation.

Usage

codecommit_create_unreferenced_merge_commit(
  repositoryName,
  sourceCommitSpecifier,
  destinationCommitSpecifier,
  mergeOption,
  conflictDetailLevel = NULL,
  conflictResolutionStrategy = NULL,
  authorName = NULL,
  email = NULL,
  commitMessage = NULL,
  keepEmptyFolders = NULL,
  conflictResolution = NULL
)

Arguments

repositoryName

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

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).

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).

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.

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.

authorName

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

email

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

commitMessage

The commit message for the unreferenced commit.

keepEmptyFolders

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.

conflictResolution

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


paws.developer.tools documentation built on Sept. 12, 2024, 6:46 a.m.