Danger

Danger runs during Slack Ruby 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 slack-ruby 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 dangerpr-bot user, look in a recent build for this project for its value.

Add Danger

Add slack-ruby-danger to Gemfile.

gem 'slack-ruby-danger', '~> 0.2.0'

Add Dangerfile

Commit a Dangerfile, eg. slack-ruby-client's Dangerfile.

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

Add Danger to Travis-CI

Add Danger to .travis.yml, eg. slack-ruby-client's Travis.yml.

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

Commit via a Pull Request

To test things out make a pull request without CHANGELOG.md changes. Iterate until green.

License

MIT License. See LICENSE for details.