pub enum TreatAsUnresolved {
ConflictMarkers,
ConflictMarkersAndAutoResolved,
Renames,
RenamesAndAutoResolvedContent,
}
Expand description
Determine what should be considered an unresolved conflict.
Note that no matter which variant, conflicts with resolution failure will always be unresolved.
Also, when one side was modified but the other side renamed it, this will not be considered a conflict, even if a non-conflicting merge happened.
Variants§
ConflictMarkers
Only consider content merges with conflict markers as unresolved.
Auto-resolved tree conflicts will not be considered unresolved.
ConflictMarkersAndAutoResolved
Consider content merges with conflict markers as unresolved, and content merges where conflicts where auto-resolved in any way, like choosing ours, theirs or by their union.
Auto-resolved tree conflicts will not be considered unresolved.
Renames
Whenever there were conflicting renames, or conflict markers, it is unresolved. Note that auto-resolved content merges will not be considered unresolved.
Also note that files that were changed in one and renamed in another will be moved into place, which will be considered resolved.
RenamesAndAutoResolvedContent
Similar to Self::Renames
, but auto-resolved content-merges will
also be considered unresolved.
Trait Implementations§
Source§impl Clone for TreatAsUnresolved
impl Clone for TreatAsUnresolved
Source§fn clone(&self) -> TreatAsUnresolved
fn clone(&self) -> TreatAsUnresolved
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more