fix: incorrect startOf/endOf behavior with +00:00 timezone

[sevtdy]

assume I'm in +08:00, when I parse time string with any regions in +00:00(like UTC, Africa/Abidjan), got the incorrect result

example:
incorrect in dayjs:

dayjs.tz('2021-04-01', 'Asia/Hong_Kong').endOf('day').format()
// "2021-04-01T23:59:59+08:00"
dayjs.tz('2021-04-01', 'Africa/Abidjan').endOf('day').format()
// "2021-04-01T15:59:59Z"
dayjs.tz('2021-04-01', 'UTC').endOf('day').format()
// "2021-04-01T15:59:59Z"

expect work like moment

moment.tz('2021-04-01', 'Asia/Hong_Kong').endOf('day').format()
// "2021-04-01T23:59:59+08:00"
moment.tz('2021-04-01', 'Africa/Abidjan').endOf('day').format()
// "2021-04-01T23:59:59Z"
moment.tz('2021-04-01', 'UTC').endOf('day').format()
// "2021-04-01T23:59:59Z"

clone form #1493
related: #1493 #1503

[iamkun]

that is weird 🤔

[aloisklink]

What might help @sevtdy is viewing https://travis-ci.com/github/iamkun/dayjs/requests.

It looks like both your earlier PRs had the error code: GitHub payload is missing a merge commit (mergeable_state: "clean", merged: false) and this current one has the error: Abuse detected.

"Abuse Detected" error

I am guessing you have made too many PRs recently, so Travis CI has blocked you: you might need to log into Travis CI with your GitHub account first (or contact support) for Travis to unblock you unfortunately (see https://travis-ci.community/t/some-pr-are-not-analyzed-with-message-abuse-detected/1191).

"GitHub payload is missing a merge commit" error

It's very weird: I believe Travis CI is looking for the field: "mergable": true and "merge_commit_sha": "...",, but your PR has both of them if you look at GitHub API:

alois@me:~$ curl -H "Accept: application/vnd.github.v3+json" https://github.com/gitapi/repos/iamkun/dayjs/pulls/1506
{
  "url": "https://github.com/gitapi/repos/iamkun/dayjs/pulls/1506",
  // ...
  "merge_commit_sha": "f1b4783ec02005944caa1db83ff05f433d1f482a",
  // ...
  "merged": false,
  "mergeable": true,
  // ...
}

Not sure what is up with this error? Maybe GitHub API was just slow a few days ago, and you just need to retry?

I had the same issue with #1448 but luckily just closing and re-opening the PR worked for me.

[sevtdy]

thank you for the tips, I try to push a new commit then it triggers Travis normally
don't know what caused this yet, but it finally works. 😂
@aloisklink