Use pip instead of conda for the docs workflow #63
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
The GitHub Actions for building the docs was using conda to setup the environment but this takes quite a while. Since it doesn't use GMT/PyGMT, there is no need for this. Switch to using pip instead to speed up the docs builds.
|
Wait for #64 to fix the broken docs build. |
|
Tests passing! Docs builds now take about 1.5 min instead of 3.5 min when using conda. |
santisoler
approved these changes
Mar 12, 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.
The GitHub Actions for building the docs was using conda to setup the environment but this takes quite a while. Since it doesn't use GMT/PyGMT, there is no need for this. Switch to using pip instead to speed up the docs builds.