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.3.1 on 2024-10-10 between 18:30 and 19:30 UTC+2
I didn’t find a way to not include the changeset from !19 (closed) in the merge request.