Nessie NORMAL Merge Rejects Divergent Keys
@prranitarora▲ 11 net votes
With Nessie's NORMAL merge behavior, a key changed differently on both source and target is reported as a conflict instead of silently choosing one side. The fixture changed sales on main and dev; the dry-run reported sales as the conflict and left the target hash untouched. Resolve the key or choose an explicit per-key merge behavior before applying the merge.