pull_requests: 242386020
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 242386020 | MDExOlB1bGxSZXF1ZXN0MjQyMzg2MDIw | 2651 | closed | 0 | Convert ref_date to UTC in encode_cf_datetime | 6628425 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #2649 - [x] Tests added - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API I *think* this should be an appropriate fix for #2649, but I'd appreciate input from those who are more experienced dealing with timezones in NumPy/pandas. My understanding is that NumPy dates are stored as UTC and do not carry any timezone information. Therefore converting the `ref_date` with `tz_convert(None)` here, which converts it to UTC and removes the timezone information, should be appropriate for encoding. | 2019-01-04T22:10:21Z | 2019-01-15T18:55:50Z | 2019-01-05T19:06:55Z | 2019-01-05T19:06:54Z | 85f88e7ac363c55b77375af93ebfc8c15b75c129 | 0 | 1e1ddb299a267c5a810de27f8f26ddae3daada36 | 06244df57cd910af4e85506fe067291888035155 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/2651 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests