New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Gemnasium badge #1320

Merged
merged 1 commit into from Oct 5, 2018

Conversation

Projects
None yet
2 participants
@orien
Contributor

orien commented Oct 5, 2018

Summary

Gemnasium has been closed.

Gemnasium has been acquired by GitLab in January 2018. Since May 15, 2018, the services provided by Gemnasium are no longer available.

The Gemnasium badge displayed on the Readme shows:

Dependency Status

Let's remove it.

Details

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Refactor (code change that does not change external functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I've added tests for my code
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
Remove Gemnasium badge
Gemnasium has been closed.

> Gemnasium has been acquired by GitLab in January 2018. Since May 15, 2018, the services provided by Gemnasium are no longer available.

Let's remove it.

@olleolleolle olleolleolle merged commit 61ce5ab into cucumber:master Oct 5, 2018

0 of 7 checks passed

ci/circleci: jruby Your tests failed on CircleCI
Details
ci/circleci: publish Your tests failed on CircleCI
Details
ci/circleci: ruby-2.2 Your tests failed on CircleCI
Details
ci/circleci: ruby-2.3 Your tests failed on CircleCI
Details
ci/circleci: ruby-2.4 Your tests failed on CircleCI
Details
ci/circleci: ruby-2.5 Your tests failed on CircleCI
Details
continuous-integration/appveyor/pr AppVeyor build failed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment