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/2921#issuecomment-490177469,https://api.github.com/repos/pydata/xarray/issues/2921,490177469,MDEyOklzc3VlQ29tbWVudDQ5MDE3NzQ2OQ==,6628425,2019-05-07T17:37:28Z,2019-05-07T17:37:28Z,MEMBER,"> We already have special treatment for time_bounds in the decode step. It makes sense to treat it specially in the encode step.

+1 I didn't fully appreciate how strict the CF conventions were regarding this at the time of #2571.  Where it is unambiguous I agree we should make an effort to comply (or preserve compliance).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,437418525