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

add travis support #11

merged 2 commits into from Dec 4, 2017


None yet
2 participants

simbabque commented Nov 29, 2017

This is my entry for the Pull Request Challenge 2017 in November.

The commit adds a .travis.yml file, which will enable Travis-CI and support for this project. In case you're not familiar how those work, here's a short description.

Both services are free for open source. You need to make your own account by signing in with your github account. You then sync your github repositories and select the ones you want. A description for the continuous integration system can be found at, and for the test coverage reports at

Travis CI will then run whenever someone sends a PR or you push a commit, and it might send you a ton of emails with reports that you can turn off if you don't want them. There are jobs in Travis for all common Perl versions. One of them will report test coverage statistics to Coveralls, where you can then inspect it in detail.

I've set up both of them for my fork. You can check them out here:

Both of those services have fancy badges that will display directly on github. I've included those in the file, but not in the POD. They will initially show an unknown build because they point to your master branch, which doesn't have the config file yet and is not set up.

If you need help setting these things up or have additional questions, feel free to ask. I consider these very useful tools that help the maintainer as well as other people supplying PRs.

@simbabque simbabque changed the title from add .travis.yml to add travis support Nov 29, 2017

@einhverfr einhverfr merged commit 4b13984 into Template-Toolkit-Latex:master Dec 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment