Skip to content

Test out speed of pydata-sphinx-theme 0.23.0rc0 - #20505

Draft
Cadair wants to merge 3 commits into
astropy:mainfrom
Cadair:test-pst-0.23rc0
Draft

Cadair wants to merge 3 commits into
astropy:mainfrom
Cadair:test-pst-0.23rc0

Conversation

@Cadair

@Cadair Cadair commented Sep 30, 2026

Copy link
Copy Markdown
Member

Description

This tests the build speed of the docs with pydata/pydata-sphinx-theme#2500

AI Disclosure

N?A

  • I certify that I am human and that I take full responsibility for this pull request including all interactions with reviewers.

Merge method

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@github-actions github-actions Bot added the Docs label Sep 30, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@Cadair

Cadair commented Sep 30, 2026 •

Copy link
Copy Markdown
Member Author

Last build on RTD (with full sidebar enabled): 33m 5s
image

This PR build (with collapse navigation False to match): 13m 38s
image

That's 2.4x faster 🏎️

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Docs Upstream Action Required Was: Upstream Fix Required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants