pub enum ResolutionFailure {
OursRenamedTheirsRenamedDifferently {
merged_blob: Option<ContentMerge>,
},
OursModifiedTheirsDirectoryThenOursRenamed {
renamed_unique_path_to_modified_blob: BString,
},
OursAddedTheirsAddedTypeMismatch {
their_unique_location: BString,
},
OursModifiedTheirsRenamedTypeMismatch,
OursDeletedTheirsRenamed,
OursModifiedTheirsDeleted,
Unknown,
}
Expand description
Describes of a conflict involving our change and their failed to be resolved.
Variants§
OursRenamedTheirsRenamedDifferently
ours was renamed, but theirs was renamed differently. Both versions will be present in the tree,
Fields
merged_blob: Option<ContentMerge>
If Some(…)
, the content of the involved blob had to be merged.
OursModifiedTheirsDirectoryThenOursRenamed
ours was modified, but theirs was turned into a directory, so ours was renamed to a non-conflicting path.
Fields
OursAddedTheirsAddedTypeMismatch
ours was added (or renamed into place) with a different mode than theirs, e.g. blob and symlink, and we kept
the symlink in its original location, renaming the other side to their_unique_location
.
Fields
OursModifiedTheirsRenamedTypeMismatch
ours was modified, and they renamed the same file, but there is also a non-mergable type-change. Here we keep both versions of the file.
OursDeletedTheirsRenamed
ours was deleted, but theirs was renamed.
OursModifiedTheirsDeleted
ours was modified and theirs was deleted. We keep the modified one and ignore the deletion.
Unknown
ours and theirs are in an untested state so it can’t be handled yet, and is considered a conflict without adding our or their side to the resulting tree.
Trait Implementations§
Source§impl Clone for ResolutionFailure
impl Clone for ResolutionFailure
Source§fn clone(&self) -> ResolutionFailure
fn clone(&self) -> ResolutionFailure
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more