I ended up having to request the existing Travis status images and parse the headers to work out the status, much like the existing Coveralls implementation. There were two main reasons for this:
I couldn't figure out how to how to get the build status for the last completed build for a given branch via the API, which is how the built-in Travis images behave - even the Travis CLI tool doesn't do this.
The Travis API for getting the most recent build does not currently support branch names that contain a slash, which is quite common (see travis-ci/travis-ci#1614).
I also made a small update to the deploy target to allow deploying from any branch, let me know if that's not cool :)
espadrine
commented
10 years ago
As discussed in #24.
Demo URL: http://salty-beyond-1018.herokuapp.com/
I ended up having to request the existing Travis status images and parse the headers to work out the status, much like the existing Coveralls implementation. There were two main reasons for this:
I also made a small update to the deploy target to allow deploying from any branch, let me know if that's not cool :)