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/pull/4599#issuecomment-732354583,https://api.github.com/repos/pydata/xarray/issues/4599,732354583,MDEyOklzc3VlQ29tbWVudDczMjM1NDU4Mw==,13301940,2020-11-23T18:47:37Z,2020-11-23T18:47:37Z,MEMBER,Oooh I see... Thank you for the clarification,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,748264086
https://github.com/pydata/xarray/pull/4599#issuecomment-732304737,https://api.github.com/repos/pydata/xarray/issues/4599,732304737,MDEyOklzc3VlQ29tbWVudDczMjMwNDczNw==,13301940,2020-11-23T17:20:49Z,2020-11-23T17:22:18Z,MEMBER,"> we decided to mark the upstream-dev CI as allowed failure. If there's a way to mark the PR CI as such,

If I understand this correctly, this is something that can be done via the branch protection settings from the repo settings.

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,748264086
https://github.com/pydata/xarray/pull/4599#issuecomment-732280083,https://api.github.com/repos/pydata/xarray/issues/4599,732280083,MDEyOklzc3VlQ29tbWVudDczMjI4MDA4Mw==,13301940,2020-11-23T16:41:12Z,2020-11-23T16:41:12Z,MEMBER,"> great, thanks again, @andersy005. Let's merge now and leave the choice between the old and new PR CI to a different PR.

Of course! I'm curious, are there any benefits to keeping the old azure upstream-dev CI around?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,748264086