#[non_exhaustive]pub struct CreateUnreferencedMergeCommitInput {
pub repository_name: Option<String>,
pub source_commit_specifier: Option<String>,
pub destination_commit_specifier: Option<String>,
pub merge_option: Option<MergeOptionTypeEnum>,
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)§
This struct is marked as non-exhaustive
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 create the unreferenced merge commit.
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).
merge_option: Option<MergeOptionTypeEnum>
The merge option or strategy you want to use to merge the code.
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.
The name of the author who created the unreferenced commit. This information is used as both the author and committer for the commit.
email: Option<String>
The email address for the person who created the unreferenced commit.
commit_message: Option<String>
The commit message for the unreferenced commit.
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§
Source§impl CreateUnreferencedMergeCommitInput
impl CreateUnreferencedMergeCommitInput
Sourcepub fn repository_name(&self) -> Option<&str>
pub fn repository_name(&self) -> Option<&str>
The name of the repository where you want to create the unreferenced merge commit.
Sourcepub fn source_commit_specifier(&self) -> Option<&str>
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).
Sourcepub fn destination_commit_specifier(&self) -> Option<&str>
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).
Sourcepub fn merge_option(&self) -> Option<&MergeOptionTypeEnum>
pub fn merge_option(&self) -> Option<&MergeOptionTypeEnum>
The merge option or strategy you want to use to merge the code.
Sourcepub fn conflict_detail_level(&self) -> Option<&ConflictDetailLevelTypeEnum>
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.
Sourcepub fn conflict_resolution_strategy(
&self,
) -> Option<&ConflictResolutionStrategyTypeEnum>
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.
The name of the author who created the unreferenced commit. This information is used as both the author and committer for the commit.
Sourcepub fn email(&self) -> Option<&str>
pub fn email(&self) -> Option<&str>
The email address for the person who created the unreferenced commit.
Sourcepub fn commit_message(&self) -> Option<&str>
pub fn commit_message(&self) -> Option<&str>
The commit message for the unreferenced commit.
Sourcepub fn keep_empty_folders(&self) -> Option<bool>
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.
Sourcepub fn conflict_resolution(&self) -> Option<&ConflictResolution>
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.
Source§impl CreateUnreferencedMergeCommitInput
impl CreateUnreferencedMergeCommitInput
Sourcepub fn builder() -> CreateUnreferencedMergeCommitInputBuilder
pub fn builder() -> CreateUnreferencedMergeCommitInputBuilder
Creates a new builder-style object to manufacture CreateUnreferencedMergeCommitInput
.
Trait Implementations§
Source§impl Clone for CreateUnreferencedMergeCommitInput
impl Clone for CreateUnreferencedMergeCommitInput
Source§fn clone(&self) -> CreateUnreferencedMergeCommitInput
fn clone(&self) -> CreateUnreferencedMergeCommitInput
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for CreateUnreferencedMergeCommitInput
impl PartialEq for CreateUnreferencedMergeCommitInput
Source§fn eq(&self, other: &CreateUnreferencedMergeCommitInput) -> bool
fn eq(&self, other: &CreateUnreferencedMergeCommitInput) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for CreateUnreferencedMergeCommitInput
Auto Trait Implementations§
impl Freeze for CreateUnreferencedMergeCommitInput
impl RefUnwindSafe for CreateUnreferencedMergeCommitInput
impl Send for CreateUnreferencedMergeCommitInput
impl Sync for CreateUnreferencedMergeCommitInput
impl Unpin for CreateUnreferencedMergeCommitInput
impl UnwindSafe for CreateUnreferencedMergeCommitInput
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);