Matt Johnson-Pint

Chrome gives `Africa/Abidjan` for me when set to UTC on Windows. Either way, the bug is the same. Yes, I will look into this. Note that if your customers are...

Note that you can create a moment in local mode from UTC-based input (having the `Z`), which will have the same effect. `moment('2016-01-01T00:00:00.000Z')` But yes, it's a bug. Or rather,...

Sorry for the delayed response. Yes, this project is still being maintained, but I'm in dire need of additional maintainers. Anyone wanting to step up to the plate should DM...

To clarify: ```js moment.tz.moveInvalidForward //=> true (the default) moment.tz('2018-03-25T01:00:00', 'Europe/London').format() //=> "2018-03-25T02:00:00+01:00" (correct) moment.tz('2018-03-25T00:00:00', 'Europe/London').hours(1).format() //=> "2018-03-25T00:00:00Z" (incorrect)

What would trigger it?

There are instructions in [the moment-timezone contributing guide](https://github.com/moment/moment-timezone/blob/develop/contributing.md). Though I've done it a couple of times and gotten it wrong somehow. Usually @timrwood does these. The other pain is that...

Oh, and don't forget publishing to all of the package repositories and CDNs.

Sort of. To be technically accurate, London is never on UTC. For part of the year it's on GMT, which just happens to be aligned with UTC+0. Though they would...

Really for our purposes, the main reason is because `isUTC() === true` would lead you to believe the value was in UTC mode, such as created with `moment.utc(...)` or converted...

Yeah, I really need to get them to change that to `(UTC+00:00)` in the display string. :wink: