Test on Travis CI #23
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
|
I'm not sure why this pull request got automatically merged. I'll look into using Travis CI. |
|
I guess this got automatically merged because its commits were also included in the merged #24. |
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.
To ensure quality, it's a good idea to add a CI server. These can run all the tests for each commit, and are especially useful to show whether tests pass or fail for PRs.
Travis CI is popular and free for open-source projects.
It uses a
.travis.ymlfile for config, which says which Python versions to test, what to install, and what to test.Here's what an example build looks like:
https://travis-ci.org/hugovk/python-path-specification/builds/459083149
Please enable this repo at https://travis-ci.org/cpburnz/python-path-specification