Replies: 1 comment
-
Only thing left is now to figure out how to change the RTD reference repo (currently my fork) to point here instead, but in a 'safe' way... I was a bit concerned earlier when I released 1.4.3 ... because I no longer remember how I update the docs on RTD. But apparently, years ago (lol) I had 'slaved' the RTD pages to my fork, and it triggers on last master update and/or last pushed tags. So the docs got updated quite seamlessly (as long as I don't forget to push the tags into my fork). However this means that updating the docs relies on me. How do I delegate and/or change this so that it tracks this repo instead, but in a 'safe-ish' way (because I'm not yet sure of the effects if I actually do that). |
Beta Was this translation helpful? Give feedback.
-
I am soooo thankful that we had created
release.py
andhousekeep.py
.That makes it relatively easy for me to get back in the 'produce and release' flow.
All FOSS projects should include similar convenience scripts, if only to help long-absent maintainers to remember how to do things!
Beta Was this translation helpful? Give feedback.
All reactions