Switch to GitHub actions for CI#24
Merged
Merged
Conversation
Contributor
Author
|
Hi. Just a quick reminder about this PR; the circle CI workflow isn't working as far as I can tell from here and is tied to an account, whereas GitHub actions work in context of the repository and are free for open source repositories like this. If there are more changes needed for the test.yml (e.g. matrix testing etc) then happy to try and add if needed. |
awkay
approved these changes
Sep 22, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It looks as if the CircleCI workflow isn't working for unit tests, but this repo is already using GitHub actions to generate the documentation. This PR creates a new GitHub workflow and removes the CircleCI configuration. This appears to work in my own fork (see https://github.com/wardle/eql/actions/runs/16803552265/job/47590263992) but I am not sure if it will interact with the documentation workflows - it should not.