#[non_exhaustive]
pub struct MergePullRequestByThreeWayInput { pub pull_request_id: Option<String>, pub repository_name: Option<String>, pub source_commit_id: Option<String>, pub conflict_detail_level: Option<ConflictDetailLevelTypeEnum>, pub conflict_resolution_strategy: Option<ConflictResolutionStrategyTypeEnum>, pub commit_message: Option<String>, pub author_name: Option<String>, pub email: Option<String>, pub keep_empty_folders: bool, pub conflict_resolution: Option<ConflictResolution>, }

Fields (Non-exhaustive)

This struct is marked as 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.
pull_request_id: Option<String>

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

repository_name: Option<String>

The name of the repository where the pull request was created.

source_commit_id: Option<String>

The full commit ID of the original or updated commit in the pull request source branch. Pass this value if you want an exception thrown if the current commit ID of the tip of the source branch does not match this commit ID.

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.

commit_message: Option<String>

The commit message to include in the commit information for the merge.

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.

keep_empty_folders: bool

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If 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

Consumes the builder and constructs an Operation<MergePullRequestByThreeWay>

Creates a new builder-style object to manufacture MergePullRequestByThreeWayInput

The system-generated ID of the pull request. To get this ID, use ListPullRequests.

The name of the repository where the pull request was created.

The full commit ID of the original or updated commit in the pull request source branch. Pass this value if you want an exception thrown if the current commit ID of the tip of the source branch does not match this commit ID.

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.

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 commit message to include in the commit information for the merge.

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

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

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If true, a .gitkeep file is created for empty folders. The default is false.

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

Trait Implementations

Returns a copy of the value. Read more

Performs copy-assignment from source. Read more

Formats the value using the given formatter. Read more

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

This method tests for !=.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Instruments this type with the provided Span, returning an Instrumented wrapper. Read more

Instruments this type with the current Span, returning an Instrumented wrapper. Read more

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

The resulting type after obtaining ownership.

Creates owned data from borrowed data, usually by cloning. Read more

🔬 This is a nightly-only experimental API. (toowned_clone_into)

Uses borrowed data to replace owned data, usually by cloning. Read more

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

Attaches the provided Subscriber to this type, returning a WithDispatch wrapper. Read more

Attaches the current default Subscriber to this type, returning a WithDispatch wrapper. Read more