Skip to content

--no-time-shift not respected when creating SEvents

meg create S1234 always creates events at the current time, regardless of whether --time-shift or --no-time-shift was used, unlike meg create G1234. This would be a nice feature to add, when wanting to copy specific events from one instance to another (e.g., production to dev).

Edited by Daniel Wysocki