Switching from CircleCI to GitHub Actions #1038
Open
Conversation
This file contains hidden or 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
Pauan
force-pushed
the
feat/github-actions
branch
from
6d7992a to
756d8f0
Compare
Pauan
force-pushed
the
feat/github-actions
branch
from
756d8f0 to
f9a6be9
Compare
Pauan
force-pushed
the
feat/github-actions
branch
from
84f8990 to
22ea953
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We've had some issues with CircleCI, especially with permissions.
We currently use both CircleCI and GitHub Actions. This consolidates everything to only use GitHub Actions.
This simplifies the CI, and should fix the permission issues. This also allows us to re-run spurious tests.