Skip to content

linux-build label, windows-build label, nuget badge for ScriptCs.Hosting and coverity badge#889

Merged
khellang merged 4 commits intoscriptcs:devfrom
adamralph:badges
Jan 4, 2015
Merged

linux-build label, windows-build label, nuget badge for ScriptCs.Hosting and coverity badge#889
khellang merged 4 commits intoscriptcs:devfrom
adamralph:badges

Conversation

@adamralph
Copy link
Copy Markdown
Contributor

The coverity badge is static because shields.io doesn't support it yet and their own badge (https://scan.coverity.com/projects/2356/badge.svg?flat=1) doesn't have the right styling.

@adamralph
Copy link
Copy Markdown
Contributor Author

@khellang
Copy link
Copy Markdown
Member

khellang commented Jan 4, 2015

Is it time to introduce a table in there? There's quite a bit of badges in the top now. It's wrapping on this screen 😝

@adamralph
Copy link
Copy Markdown
Contributor Author

As a start we could drop them down a line, to below the 'scriptcs' header.

@khellang
Copy link
Copy Markdown
Member

khellang commented Jan 4, 2015

Sure. Ideally I'd like a "build matrix", like this:

Platform Status
Windows Windows Build Status
*NIX *nix Build Status
Coverity Coverity Scan Build Status

@adamralph
Copy link
Copy Markdown
Contributor Author

I dropped it down a line but it still wraps 😒

@adamralph
Copy link
Copy Markdown
Contributor Author

The table has duplication, i.e. the 'Platform' column and the badge labels.

Perhaps we could split it into two rows, e.g.

Chocolatey Version Chocolatey Downloads NuGet version (ScriptCs.Hosting)

*nix Build Status Windows Build Status Coverity Scan Build Status

@khellang
Copy link
Copy Markdown
Member

khellang commented Jan 4, 2015

I guess that'll do 😄

khellang added a commit that referenced this pull request Jan 4, 2015
linux-build label, windows-build label, nuget badge for ScriptCs.Hosting and coverity badge
@khellang khellang merged commit 5c0e00e into scriptcs:dev Jan 4, 2015
@adamralph adamralph deleted the badges branch January 4, 2015 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants