[MRG] Pin the version of the sphinx theme used #1070
Merged
Conversation
This file contains 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
betatim
force-pushed
the
fixup-docs-theme
branch
from
16ddca3
to
c693dc5
Compare
|
I was thinking the same thing, we should really start releasing versions on the pydata theme |
yuvipanda
pushed a commit
to jupyterhub/helm-chart
that referenced
this pull request
Feb 26, 2020
manics
added a commit
to manics/jupyterhub
that referenced
this pull request
Feb 27, 2020
manics
added a commit
to manics/zero-to-jupyterhub-k8s
that referenced
this pull request
Feb 27, 2020
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.
Closes #1069
This should trigger a rebuild of our docs and pins us to a specific revision of the theme. We should move the pin forwards every once in a while to stay current. With a pinned revision we can explicitly check that things still work when we do update.