badges / buckler Goto Github PK

Reticketed from badges/shields#84.

I believe @olivierlacan has asked for /first/second.png?color. I like the idea of prefixing the path with /v1, though that breaks backcompat (not too worried about that yet?).

SSIA

Not sure what's causing that, bad GitHub cache?

Allow generating a single image that includes multiple statuses

Check if its faster to rerender the text for the shadow, or to copy the bitmap and recolor it (recoloring is probably faster). Use the fastest.

GitHub caches pages, so status images should be served over HTTPS as a work-around.

This way, the badges would still look good on high-resolution displays.

Ref. h5bp/lazyweb-requests#150

I don't think this is just due to the images being 1x — lots of 1x images are at least still as readable as they were before on a 2x screen. For some reason, the particular antialiasing and shadows on these badges are super hard to read on a 2x screen. Fuzzy and illegible and make my eyes hurt.

Reticketed from badges/shields#84.

Currently we hit an HTTP backend to resolve a token such as (travis-ci, rails/rails) into (build, passing). This will need to be a well-documented API as it will be how we on-board third-party services.

Set proper headers for caching and stuff. That will make stuff go faster!

package up all assets into a single binary that can be attached to github releases

I'm trying to create a badge that says "<script>" and "</script>" and the site yields 503s whenever I include < or > or / -- even if I url-encode and/or http-encode the parameter. I suspect many non-[a-zA-Z0-9] have a similar concern.

generate shields from the cli

@olivierlacan What do you want to block this on? At least until the URLs are revised (#19), eh? Though if we break backcompat there w/ /v1 then I suppose it doesn't hurt further to cut over sooner.

Please change ShaaS in BadaaS 🐸

[![deprecated](http://badges.github.io/stability-badges/dist/deprecated.svg)](http://github.com/badges/stability-badges)

I've noticed that images for Shippable builds are not working for branches except master.

Thus the following three images always yield the same result (from master):

https://img.shields.io/shippable/54d119db5ab6cc13528ab183/master.svg
https://img.shields.io/shippable/54d119db5ab6cc13528ab183/staging.svg
https://img.shields.io/shippable/54d119db5ab6cc13528ab183/production.svg

As soon as we trigger a build on master, all three badges change to build | pending and return to build | passing after it completes. A build on staging and production do not yield any change.

Thanks for this project! It's awesome!

I'd like to know if it's possible to get the shields in different scale, like the "retina" version of shields. Something like "@2x" after the shield name or some other param to assign the size of the required image.

Allow using colors for the vendor section

I'm having trouble to get shields with a slash, both on the vendor and on the status.

I've also tried the URI code for slash %2F but there's no change.

Add a header that contains the deployed git describe output