travis-ci integration #40
Closed
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
|
This has been the impetus I guess to finally actually look into travis-ci. I'm still reading more and will decide later whether or not to enable for this project. |
michalkaptur
force-pushed
the
travis_ci_support
branch
from
1fafeb5
to
bff717e
Compare
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.
Basic Travis CI configuration, which runs all tests using several versions of python.
Native integration with GitHub allows users to see the tests status in the PRs description. There could be a rule, to require green CI result for PR in order to merge.
When merged, there would be also CI indicator available, like the one below:
