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-830866994,https://api.github.com/repos/pydata/xarray/issues/5244,830866994,MDEyOklzc3VlQ29tbWVudDgzMDg2Njk5NA==,5635139,2021-05-02T20:28:15Z,2021-05-02T20:28:15Z,MEMBER,"I _think_ both of those should be script-able as actions:

> git merge upstream/stable

This could run on each commit to stable, opening a PR to master if required, I think

> Update the stable branch (used by ReadTheDocs) and switch back to master:

This could run on each tag, like the push to PyPI.

There's one action of ""update the release tag in RTD"" which may still be manual


(though no need to do them now, I generally have tried to make the process 25% easier each release, I think these incremental PRs are ideal)","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,873842812
https://github.com/pydata/xarray/pull/5244#issuecomment-830746026,https://api.github.com/repos/pydata/xarray/issues/5244,830746026,MDEyOklzc3VlQ29tbWVudDgzMDc0NjAyNg==,5635139,2021-05-02T05:28:04Z,2021-05-02T05:28:04Z,MEMBER,"Excellent! Thanks a lot @andersy005 .

We could change the ""how to release"" steps too, in another PR is fine (or I can do it).

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,873842812