Automate common code review chores with http://danger.systems.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib/ruby-grape-danger
spec
.gitignore
.rspec
.rubocop.yml
.rubocop_todo.yml
.travis.yml
CHANGELOG.md
CONTRIBUTING.md
Dangerfile
Gemfile
LICENSE
README.md
RELEASING.md
Rakefile
ruby-grape-danger.gemspec

README.md

Danger

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

Build Status

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.