Add support for customizing badge colors

[jgranick]

Hey guys,

I am using the "GitHub" style badge in order to denote the latest release of https://github.com/openfl/openfl on Haxelib.

I would not expect Haxelib to be supported out of the box on shields.io, and the Github badge is working great, except I really would like to customize the color. Could this be added? Something like this:

(but orange, using color=orange)

[espadrine]

Hi!

Badge colors are usually there to emphasize a point (such as, for tests, whether the tests pass). For versions, it distinguishes at a glance major version zero / pre-release (in the semver definition). Orange means that the provided API is unstable. Blue means stable.

We could definitely allow to override that color. Wouldn't it defeat its purpose, though?

[jgranick]

Ah, I thought it was hard-coded to use blue in order to match GitHub. In general, I believe that the standardized color codes is a good way to go, particularly when coming to build | passed or build | failed it's really clear.

Although it might ordinarily be discouraged, I feel the label value allows the tags to be used in ways, perhaps, they weren't originally intended. For example, it happens that I tag every release we make, so even though haxelib is not a supported type, I've leveraged it to give me what I want, but I didn't realize the significance. I think a color tag could do the same

Another system, "Badge Fury" (for example), uses green for versions, and one could make their badges match if they wanted: http://badge.fury.io

If you added support for doing "GitHub Issues", while specifying a tag name (at first I thought the "issues-raw" example was using a "raw" tag, but I was mistaken) then I would also be interested in replicating a waffle.io badge. By doing a Github Issues badge for issues marked "ready" only, I could recreate their badge. However, in this case, it would be great as well to use a color tag to use their same light blue hue, so it's the same Waffle badge, but flat and modern looking.

I think adding a color tag would lend itself to creative new ways to leverage your existing functionality 😄

[espadrine]

Waffle support would definitely be great. So far, the issue isn't solved, although sending requests directly to GitHub may solve it.

[nijikokun]

Badge colors are usually there to emphasize a point (such as, for tests, whether the tests pass). For versions, it distinguishes at a glance major version zero / pre-release (in the semver definition). Orange means that the provided API is unstable. Blue means stable.

What do you mean when you say "API is unstable"

[jgranick]

From http://semver.org:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

[zbeekman]

I would like to be able to have some badge color override too

[dmarcelino]

👍 for badge color override

[montanaflynn]

+1

Could work just like the style through a query string such as ?color=brightgreen

[timothyfcook]

This relates heavily to #401 e.g. there is no ?color=purple option which is necessary for a Heroku deploy button.

[espadrine]

@timothyfcook Isn't that orthogonal to the issue? We can definitely do this: http://img.shields.io/badge/heroku-deploy-7251C2.svg.

[timothyfcook]

Cool. That's great. Maybe it's as simple as adding a bit to the Style section to explain that you can use hexadecimal color codes.

[espadrine]

It's meant to be implicit in the segment on how to build custom badges (see the badge color on the right): http://shields.io/#your-badge

[timothyfcook]

Just noticed that. Maybe let's highlight it somehow. Very subtle.

[miroswan]

How would you add color to a downloads badge?

[espadrine]

There is a PR for overriding colors now: #547

[paulmelnikow]

Related: #842

[paulmelnikow]

@RedSparr0w