Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix GitHub Actions #434

Merged
merged 2 commits into from
Jun 16, 2023
Merged

Fix GitHub Actions #434

merged 2 commits into from
Jun 16, 2023

Conversation

forsyth2
Copy link
Collaborator

Fix GitHub Actions

@forsyth2 forsyth2 added the DevOps CI/CD, configuration, etc. label Jun 15, 2023
@forsyth2
Copy link
Collaborator Author

@xylar You mentioned in #429 (comment) "You want to avoid mixing conda-forge and pip packages whenever possible."

However, reverting that change, as done in this PR, seems to be the only way to get the GitHub Actions checks passing. I imagine the same will hold true for the equivalent zstash error: E3SM-Project/zstash#271 (comment)

@forsyth2 forsyth2 merged commit 269eef9 into main Jun 16, 2023
@forsyth2 forsyth2 deleted the fix-action branch June 16, 2023 00:48
@forsyth2 forsyth2 mentioned this pull request Jun 16, 2023
xylar pushed a commit to xylar/zppy that referenced this pull request Jun 16, 2023
* Fix GitHub Actions

* Revert sphinx-multiversion handling
forsyth2 added a commit that referenced this pull request Jun 16, 2023
* Change workflow to mamba (#429)

* Change workflow to mamba

* Fix GitHub Actions (#434)

* Fix GitHub Actions

* Revert sphinx-multiversion handling

* Get sphinx-multiversion from conda-forge

* Remove redundant dependency installation

* Switch docs workflows to mamba

---------

Co-authored-by: forsyth2 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps CI/CD, configuration, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant