This repository was archived by the owner on Jun 19, 2026. It is now read-only.
Proposal: Using GitHub actions to run tests#39
Open
arschles wants to merge 1 commit into
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds the GitHub actions go action (longer explanation of what this is) and begins running tests on GitHub actions.
Both Travis CI file and actions can co-exist, and the basic feature sets are approximately the same. The major difference is that actions are based on community contributed (sometimes GitHub curated) code, so improvements are easier.
I've also proposed this change because the Travis CI product has gone through some changes in the past few months, introducing some risk.