ruby-grape / danger

Danger

Danger runs during Grape projects' CI process, and gives you a chance to automate common code review chores.

Table of Contents

• Setup
  • Set DANGER_GITHUB_API_TOKEN in Travis-CI
  • Add Danger
  • Add Dangerfile
  • Add Danger to Travis-CI
  • Commit via a Pull Request
• License

Setup

Enable Danger for a project within the ruby-grape organization.

Set DANGER_GITHUB_API_TOKEN in Travis-CI

In Travis-CI, choose Settings and add DANGER_GITHUB_API_TOKEN in Environment Variables. Set the value to the API key for the grape-bot user, look in this build log for its value.

Add Danger

Add ruby-grape-danger to Gemfile.

gem 'ruby-grape-danger', '~> 0.1.0', require: false

Add Dangerfile

Commit a Dangerfile, eg. Grape's Dangerfile.

danger.import_dangerfile(gem: 'ruby-grape-danger')

Add Danger to Travis-CI

Add Danger to .travis.yml, eg. Grape's Travis.yml.

matrix:
  include:
    - rvm: 2.3.1
      script:
        - bundle exec danger

Commit via a Pull Request

To test things out, make a dummy entry in CHANGELOG.md that doesn't match the standard format and make a pull request. Iterate until green.

License

MIT License. See LICENSE for details.