Given that there seemed to be issues testing the changes to the site in a forked repo and that possibly messing with the settings/custom domain, I have disabled the GitHub pages from my fork, enacted the changes via Sphinx, branched them from my master into a new branch for staging the changes, and opened this PR with the target merge being into upstream/master. Hopefully this will disconnect the GitHub pages configuration settings from any updates to static files that I am attempting to publish and all will be good on the site after GitHub detects the merge into upstream/master.
@sbillinge, this seems like the next logical workflow to test and should be good to be merged whenever you're ready, although we may need to hold onto our hats to see if the lack of GitHub pages on my fork ends up causing similar problems...
Given that there seemed to be issues testing the changes to the site in a forked repo and that possibly messing with the settings/custom domain, I have disabled the GitHub pages from my fork, enacted the changes via Sphinx, branched them from my
masterinto a new branch for staging the changes, and opened this PR with the target merge being intoupstream/master. Hopefully this will disconnect the GitHub pages configuration settings from any updates to static files that I am attempting to publish and all will be good on the site after GitHub detects the merge intoupstream/master.@sbillinge, this seems like the next logical workflow to test and should be good to be merged whenever you're ready, although we may need to hold onto our hats to see if the lack of GitHub pages on my fork ends up causing similar problems...