Conversation
choldgraf
left a comment
There was a problem hiding this comment.
+1 from me, I think we are overdue for this.
I'm happy to do the manual actions that @jarrodmillman notes above if there are no objections
|
@choldgraf Any interest in making this change today? It shouldn't take long and it may be good to do it before the 0.9rc1. |
|
Normally I solved everything in my PR if we can merge it before this one that would be perfect. Also @jarrodmillman could you copy/paste the instructions to change from master to main in an issue so that it can be pinned on top of the issue list it will be perfect (I'm positive I'm going to forget and I think I wont be the only one) |
|
Great idea to pin those instructions in an issue. We can plan to close it in, say, 3 months. |
|
I added a draft of the pinned issue: |
|
Thanks so much for your help @jarrodmillman 🙏 |
f60b25a to
c842214
Compare
|
@choldgraf I think we are set to make the change. I don't have access to the repository settings, so you will need to do that. In my experience the process is painless and we have almost no remaining PRs (but they will be updated automatically). The only issue I've ever seen is that PR whose branch has been deleted are closed, but none of our existing PRs have that issue. You should be able to follow the steps I list on my first comment on this issue. |
|
OK - I have:
|
Close #549.
Here is what I think needs to be done:
mainon GitHub:mastertomain) readthedocs/readthedocs.org#7907 (comment)mainbranch as follows:The whole process should only take a few minutes. You could send an email to developers telling them about step 5, if you want.