Closed haoliangyu closed 5 years ago
Looks like we can still use img.shields.io, but we have to specify the branch. For example, the currently used CKAN provider badge is:
![travis](https://img.shields.io/travis/koopjs/koop-provider-ckan.svg?style=flat-square)
and as you noted, this is for latest build, not master. But if you add /master
to the url, we get last build of master:
![travis](https://img.shields.io/travis/koopjs/koop-provider-ckan/master.svg?style=flat-square)
Fixed what was fixable....it turns out that some of the failing/unknown badges were the repos were not configured to do Travis builds. I removed those badges altogether and replaced with an NA
in hopes of reducing confusion.
The badge of build status for plugins are now from shields.io and it displays the status of the latest build, no matter from where! It can be even a PR build.
For example, the CKAN provider has a
failed
build status at the homepageBut if I click at the status badge, the failure is from a greenkeeper PR
At the same time, the build status of the master branch is green
This can be very misleading for the user. I would suggest to use the badge image directly from Travis CI and specify the branch to
master
for stability. It is like: