html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/4670#issuecomment-742047513,https://api.github.com/repos/pydata/xarray/issues/4670,742047513,MDEyOklzc3VlQ29tbWVudDc0MjA0NzUxMw==,1217238,2020-12-09T21:01:27Z,2020-12-09T21:01:27Z,MEMBER,"> Our new scheduled nightly CI improves the situation quite a bit since we automatically get a issue containing the failures, but that means we aren't able to catch these failures before actually merging. As pointed out in [#4574 (comment)](https://github.com/pydata/xarray/issues/4574#issuecomment-725795622) that might be acceptable, though.

I agree, I think is probably an acceptable compromise.

Most bugs with upstream-dev occur with _existing_ code in xarray, not new code introduced by a PR.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,760574919