You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
don't incorrectly mark as auto-resolved conflict if there was none.
Previously it was possible to mark perfectly working content merges as conflicting
if we would choose 'our' or 'their' resolution.
when binary merges are performed, adjust the returned resolution to indicate auto-resolution.
Previously it wasn't possible to detect auto-resolution, even though it can be assumed if a
resolution mode was provided.
New Features (BREAKING)
replace tree::Options::allow_lossy_resolution with *::tree_conflicts.
That way it's possible to steer how to resolve tree-related conflicts while
making it possible to detect that a conflict happened.
Bug Fixes (BREAKING)
assure that tree::apply_index_entries() cannot unknowingly leave unconflicted and conflicted entries.
This is a massive footgun currently where incorrect usage is very likely while causing all kinds of mistakes.
Commit Statistics
12 commits contributed to the release over the course of 28 calendar days.