How
Danger is ruby gem that runs a Dangerfile. You set up a Dangerfile per-project. The Dangerfile contains a collection of home-grown rules specific to your project.
Danger should be installed via a Gemfile. Add gem "danger" to your Gemfile, then run bundle.
You can integrate Danger into your own project on any available CI service. She will run through the process with you if you run danger init after installation.
Messaging Options
Comment a message to the table:
message("You have added 3 more gems to the app.")
Declares a CI warning:
warn("You have not included a CHANGELOG entry.")
Declares a CI blocking error:
fail("Our linter has failed.")
Outputs markdown under the table:
markdown("## ")
Outputs markdown at a line in the diff:
warn("Please add your name", file: "CHANGELOG.md", line: 4)
Supports
Can run on: Circle, Travis, Jenkins, Buildkite, BuddyBuild, Semaphore, TeamCity, Xcode Bots, Drone, Surf and Bitrise.
Can chat back on: GitHub, GitLab and Bitbucket.
Can handle diffs from: Git.
Features
| SCM |
Feedback |
Inline Comments |
API Access |
| GitHub |
✅ |
✅ |
✅ |
| GitHub Enterprise |
✅ |
✅ |
✅ |
| GitLab.com |
✅ |
🚫 |
✅ |
| GitLab CE |
✅ |
🚫 |
✅ |
| GitLab EE |
✅ |
🚫 |
✅ |
| Bitbucket.org |
🚫 |
🚫 |
🚫 |
| Bitbucket Server |
✅ |
🚫 |
🚫 |