CI: share pandas setup steps #39745
Merged
CI: share pandas setup steps #39745
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
afeld
commented
Feb 11, 2021
afeld
force-pushed
the
refactor-ci-setup
branch
from
5569363 to
ed85af3
Compare
afeld
force-pushed
the
refactor-ci-setup
branch
from
ed85af3 to
3905b59
Compare
4 tasks
|
thanks @afeld |
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.
Split out from #39392. Just a refactor; puts redundant setup steps in a shared place.
To be honest, I don't actually understand why different GitHub Actions set up pandas in different ways, so didn't change that here.
The
usescalls can be moved into the composite actions once actions/runner#862 is complete, DRYing it up even more.closes #xxxxadded /passedwhatsnew entry