evolve: preserve date when resolving content-divergence (issue6202)
I didn’t find a way to not include the changeset from !19 (closed) in the merge request.
This instance will be upgraded to Heptapod 17.8.1 on 2025-03-13 between 17:00 and 18:00 UTC+2
I didn’t find a way to not include the changeset from !19 (closed) in the merge request.