pull_requests: 333805552
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 333805552 | MDExOlB1bGxSZXF1ZXN0MzMzODA1NTUy | 3459 | closed | 0 | Dataset.map | 5635139 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Helps https://github.com/pydata/xarray/issues/1251 - [x] Tests added - [x] Passes `black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API This is the first step towards organizing these functions a bit better, as outlined in https://github.com/pydata/xarray/issues/1251, https://github.com/pydata/xarray/issues/1618, https://github.com/pydata/xarray/pull/2674 While this one is a fairly easy decision, others are going to be harder. Open to a more methodical up-front process before we start making changes, if we think that's necessary. | 2019-10-29T18:46:04Z | 2019-11-09T22:08:07Z | 2019-11-09T21:10:23Z | 2019-11-09T21:10:23Z | db0f13d194845b06fa82f64574d0e78d8449ddbe | 0 | 609cb5d31a0091e2913c48465d09a0adc503b74b | bb89534687ee5dac54d87c22154d3cfeb030ce21 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/3459 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests