first shot at github actions setup #57
Merged
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
feenes
force-pushed
the
dvl/feens/github-actions
branch
2 times, most recently
from
d7f615a to
8cc074e
Compare
feenes
force-pushed
the
dvl/feens/github-actions
branch
from
27952fd to
9744942
Compare
mrch81
approved these changes
Jan 27, 2021
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.
Travis seems to be a little out of fashion and no more recommended.
Thus here a small first shot at using gitlab actions for performing CI.
At the moment travis and github are both performing CI.
If this works nicely the travis runners should be removed.
What is interesting though is, that at the moment Travis seems to run faster than github actions