You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first off - this is the best extension ever!!! - saves me over-and-over.
new specstories are using utc - probably not what most people expect.
upon a restart, previous utc-tagged spectories were all erased, and new copies of it using my localtime appeared... ok, but, this trashed all the actual file dates and times on all my old specstory files in-so-doing...
would have been better to use localtime in the firstplace, and not change/rename files (which polluted my git commit with a pile of deletes and new files)
The text was updated successfully, but these errors were encountered:
new specstories are using utc - probably not what most people expect.
We debated this long and hard internally (probably spending more time on it than we should) and ultimately decided on UTC as the best approach as we are seeing SpecStory histories getting checked into repositories a lot and are talking to teams sharing their AI interaction histories via SpecStory and they aren't all in the same TZ. We felt UTC optimized for a team setting.
I think ideally what we should do is default to UTC, but make the TZ a setting so if folks are working alone, or in the same TZ as others, they can use something that's more natural to them. Using this issue to capture this as an enhancement.
first off - this is the best extension ever!!! - saves me over-and-over.
The text was updated successfully, but these errors were encountered: