CI (DOC/WEB): replace upload to server with push to github pages repo - #66809
Open
jorisvandenbossche wants to merge 5 commits into
Open
CI (DOC/WEB): replace upload to server with push to github pages repo#66809jorisvandenbossche wants to merge 5 commits into
jorisvandenbossche wants to merge 5 commits into
Conversation
rhshadrach
requested changes
Aug 17, 2026
rhshadrach
approved these changes
Aug 20, 2026
Member
There was a problem hiding this comment.
lgtm - I figure we should merge this when the bandwidth is available to handle any issues. I think you can go ahead when ready @jorisvandenbossche, I can maybe do it next week at the earliest.
Member
Author
|
Good idea, I still some time today, but let's play safe, and I'll merge on Monday morning, then I have a full week available for follow-ups. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
xref #64703
This updates the doc build workflow to rsync to a checkout of https://github.com/pandas-dev/pandas-dev.github.io instead of to the (no longer running) server. And then creates a commit and pushes that to the repo.
Pushing to a different repo will need an access token or deploy key (to be saved as
PANDAS_DEV_GITHUB_IO_TOKEN) that can write topandas-dev/pandas-dev.github.io(still have to set this up, and check that pushing to the pages repo will be allowed that way).It seems that the deploy key is regarded as a safer option than the personal access token. And I don't think there is a way around using one of those two (except for creating a custom github app)