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/5244#issuecomment-832596969,https://api.github.com/repos/pydata/xarray/issues/5244,832596969,MDEyOklzc3VlQ29tbWVudDgzMjU5Njk2OQ==,5821660,2021-05-05T10:56:06Z,2021-05-05T10:56:06Z,MEMBER,"> This should be pretty easy if we have separate jobs for building / testing / uploads (where the upload to `pypi` is skipped unless a release was created)

I've doing this for a while now in one of my projects. Not sure if it will be used much, but users could easily install versions from `test.pypi.org` and check it. I'm not saying that pip-installing from github is too complex. Another aspect is, that you could even install the package again after upload to check that everything works. But that may be overkill.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,873842812