id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type 1118729170,PR_kwDOAMm_X84xzR0v,6211,Xfail failing test,5635139,closed,0,,,8,2022-01-30T21:42:35Z,2022-01-31T17:21:40Z,2022-01-31T01:49:10Z,MEMBER,,0,pydata/xarray/pulls/6211," As per https://github.com/pydata/xarray/issues/6209#issuecomment-1025116203","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/6211/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 919842557,MDExOlB1bGxSZXF1ZXN0NjY5MDg1OTY0,5468,Run mypy in pre-commit only in CI?,5635139,closed,0,,,8,2021-06-13T17:11:36Z,2021-06-18T19:33:14Z,2021-06-18T19:01:48Z,MEMBER,,0,pydata/xarray/pulls/5468," On top of https://github.com/pydata/xarray/pull/5467, given I'm not sure this is correct. With `additional_dependencies`, we may not need the additional CI run. But OTOH there's nothing confirming that the `additional_dependencies` has the correct dependencies and there's no material cost to the additional step.","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/5468/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 849974334,MDExOlB1bGxSZXF1ZXN0NjA4NjIwOTIw,5110,Move mypy configs from pre-commit to mypy config,5635139,closed,0,,,8,2021-04-04T22:27:15Z,2021-04-19T06:10:34Z,2021-04-14T18:43:56Z,MEMBER,,0,pydata/xarray/pulls/5110," - [x] Passes `pre-commit run --all-files` This should mean that running `mypy .` doesn't operate differently from running it in pre-commit. It's also possible I've misunderstood something about mypy configs, please let me know if so! ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/5110/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 423471477,MDExOlB1bGxSZXF1ZXN0MjYzMDM3MDIy,2831,Enable python 3.5.0-3.5.2,5635139,closed,0,,,8,2019-03-20T21:03:51Z,2019-03-22T15:12:27Z,2019-03-22T04:37:25Z,MEMBER,,0,pydata/xarray/pulls/2831, - [x] Closes some of https://github.com/pydata/xarray/issues/2830,"{""url"": ""https://api.github.com/repos/pydata/xarray/issues/2831/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 288382105,MDExOlB1bGxSZXF1ZXN0MTYyODA5ODA3,1828,pytest-ification,5635139,closed,0,,,8,2018-01-14T04:33:17Z,2018-01-15T22:25:33Z,2018-01-15T22:25:30Z,MEMBER,,0,pydata/xarray/pulls/1828,"So far, only the changes that `unittest2pytest` could fix. Need to work out how to sort through the exisiting xarray ones EDIT: ready to merge (and keen to get this in before there are divergences from other branches)","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1828/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull