Update Sauce Labs badge style & link [skip ci] #417
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* update Sauce Labs badge visual style to match Travis CI style, which also matches the thickness for them to fit on a single line together * point Sauce Labs badge URL to the live status page for all Metal.js builds, instead of a specific build, as that's not really useful as it becomes out-of-date immediately * update Travis CI badge to use the `develop` branch instead of `master`, since ongoing development happens on `develop` and `master` is only updated for each release, so it doesn't change very often * move invitation to join the Slack community from between the two build status badges to below the official website as they are both communication channels, which allows us to put the two build status badges close together at the top of the page
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
matches the thickness for them to fit on a single line together
instead of a specific build, as that's not really useful as it becomes
out-of-date immediately
developbranch instead ofmaster, sinceongoing development happens on
developandmasteris only updated for eachrelease, so it doesn't change very often
badges to below the official website as they are both communication channels,
which allows us to put the two build status badges close together at the top
of the page