Struct aws_sdk_codecommit::operation::merge_branches_by_squash::MergeBranchesBySquashInput

#[non_exhaustive]
pub struct MergeBranchesBySquashInput {
    pub repository_name: Option<String>,
    pub source_commit_specifier: Option<String>,
    pub destination_commit_specifier: Option<String>,
    pub target_branch: Option<String>,
    pub conflict_detail_level: Option<ConflictDetailLevelTypeEnum>,
    pub conflict_resolution_strategy: Option<ConflictResolutionStrategyTypeEnum>,
    pub author_name: Option<String>,
    pub email: Option<String>,
    pub commit_message: Option<String>,
    pub keep_empty_folders: Option<bool>,
    pub conflict_resolution: Option<ConflictResolution>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

repository_name: Option<String>

The name of the repository where you want to merge two branches.

source_commit_specifier: Option<String>

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

destination_commit_specifier: Option<String>

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

target_branch: Option<String>

The branch where the merge is applied.

conflict_detail_level: Option<ConflictDetailLevelTypeEnum>

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.

conflict_resolution_strategy: Option<ConflictResolutionStrategyTypeEnum>

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.

author_name: Option<String>

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

email: Option<String>

The email address of the person merging the branches. This information is used in the commit information for the merge.

commit_message: Option<String>

The commit message for the merge.

keep_empty_folders: Option<bool>

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.

conflict_resolution: Option<ConflictResolution>

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

Implementations

impl MergeBranchesBySquashInput

pub fn repository_name(&self) -> Option<&str>

The name of the repository where you want to merge two branches.

pub fn source_commit_specifier(&self) -> Option<&str>

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

pub fn destination_commit_specifier(&self) -> Option<&str>

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

pub fn target_branch(&self) -> Option<&str>

The branch where the merge is applied.

pub fn conflict_detail_level(&self) -> Option<&ConflictDetailLevelTypeEnum>

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.

pub fn conflict_resolution_strategy( &self ) -> Option<&ConflictResolutionStrategyTypeEnum>

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.

pub fn author_name(&self) -> Option<&str>

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

pub fn email(&self) -> Option<&str>

The email address of the person merging the branches. This information is used in the commit information for the merge.

pub fn commit_message(&self) -> Option<&str>

The commit message for the merge.

pub fn keep_empty_folders(&self) -> Option<bool>

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.

pub fn conflict_resolution(&self) -> Option<&ConflictResolution>

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

impl MergeBranchesBySquashInput

pub fn builder() -> MergeBranchesBySquashInputBuilder

Creates a new builder-style object to manufacture MergeBranchesBySquashInput.

Trait Implementations

impl Clone for MergeBranchesBySquashInput

fn clone(&self) -> MergeBranchesBySquashInput

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MergeBranchesBySquashInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for MergeBranchesBySquashInput

fn eq(&self, other: &MergeBranchesBySquashInput) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for MergeBranchesBySquashInput