pull_requests: 348462006
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 348462006 | MDExOlB1bGxSZXF1ZXN0MzQ4NDYyMDA2 | 3589 | closed | 0 | Resolve the version issues on RTD | 14808389 | The trick mentioned in https://github.com/pydata/xarray/issues/3567#issuecomment-561270215 works locally, but I don't know whether that's also the case for RTD. Since my own RTD setup cannot go past the environment creation stage: can someone with the appropriate rights on the official setup try this out for me? Adding `xarray` to `doc.yml` is something temporary that has to be removed before the merge, but I think it is necessary to make sure the version collision occurs. - [x] Closes #3567 - [x] Passes `black . && mypy . && flake8` | 2019-12-03T17:39:23Z | 2019-12-03T19:18:24Z | 2019-12-03T18:59:41Z | 2019-12-03T18:59:40Z | ed05f9862622b00f40f7b9b99ccdb0ab3766ff0f | 0 | 1a075fe84273ef06942f43d38d6645cc8f042dd8 | 69c85b85a1ef5d13b6ca51b6b655a1f719cc5abf | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/3589 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests