Use actions/setup-python in publish-docs #2021
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
instead of managing a virtualenv directly which hopefully resolves the problem with mkdocs not finding its extensions
meatballhat
force-pushed
the
publish-docs-python-shuffle
branch
from
4ee19b0 to
499d63d
Compare
dearchap
approved these changes
Nov 30, 2024
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.
instead of managing a virtualenv directly which hopefully resolves the problem with mkdocs not finding its extensions.
Update: bumping the version of
mkdocs-materialseems to have done the trickWhat type of PR is this?
What this PR does / why we need it:
so that documentation is published from
mainandv3tags againWhich issue(s) this PR fixes:
N/A ; maybe this comment