Use UTC for timestamps when creating a migration #242
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Are you compiling |
|
Native goose with |
|
I'm worried this would cause issues for someone out there. Fwiw you can set In a breaking |
|
Oh duh why didn’t I think of that 😄
…On Sun, 24 Oct 2021, at 13:19, Michael Fridman wrote:
I'm worried this would cause issues for someone out there. Fwiw you can set `TZ="UTC" goose ...` ?
In a breaking `/v4` we can set UTC as a default for timestamps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEQ2KAEEZET6VAYMIHTIHTUIRS55ANCNFSM4X2WYJJQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
With my team we are facing this exact same issue of having the timestamp utc specified, is there any news on this topic ? Thanks ! |
…tamp-on-create # Conflicts: # create.go
|
This will be merged and released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So, I understand that there is prior art here (#38, #50, #63), but my team is using timestamped versions and switching to sequential numbering is not an option at this time. We're split across multiple timezones and in order to keep things a little more sane, UTC would be a welcome change for the timestamps. Maybe in the future we can migrate over to sequential, but this is where we are at.