-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Run exercise tests through Travis #104
Labels
Comments
I personally have little experience in Travis, but am more than happy to look in to this if no-one else has experience - let me know 👍 |
I've got some experience with Travis. I might be able to work on this if I have time. |
Sounds good to me @Smarticles101 🙂 |
Closed
@Smarticles101 any updates on this? If you are too busy I can give it a try this weekend. |
Fixed via #148 (Thanks! 🙂 ) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in #4, for each pull request, a run through all exercise tests would help maintainers quickly identify if the submission causes the tests to fail.
Travis is currently used to lint submissions.<- incorrect! configlet lint is pulled in, but #116 talks about code linting.The text was updated successfully, but these errors were encountered: