🚫 Stop saying "you forgot to …" in code review (in Ruby)
Alternatives To Danger
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Reviewdog6,6991282 days ago155June 19, 2023115mitGo
🐶 Automated code review tool integrated with any code analysis tools regardless of programming language
Danger5,2231,30268a day ago179June 06, 2023158mitRuby
🚫 Stop saying "you forgot to …" in code review (in Ruby)
Danger Js5,0102,26259810 days ago310July 31, 2023161mitTypeScript
⚠️ Stop saying "you forgot to …" in code review
4 days ago6gpl-3.0CSS
nodejsscan is a static security code scanner for Node.js applications.
3 months ago64mitRuby
Automated code review for GitHub pull requests.
Awesome Open Source Supporters585
23 days agocc0-1.0
⭐️ A curated list of companies that offer their services for free to Open Source projects
Cpp Project551
3 months ago1unlicenseCMake
Boiler plate template for C++ projects, with CMake, Doctest, Travis CI, Appveyor, Github Actions and coverage reports.
Chatgpt Action491
6 months ago13mitJavaScript
Let ChatGPT review PRs for you
Woke36418 months ago71July 28, 202234mitGo
Detect non-inclusive language in your source code.
Njsscan3181a month ago32January 31, 20227lgpl-3.0JavaScript
njsscan is a semantic aware SAST tool that can find insecure code patterns in your Node.js applications.
Alternatives To Danger
Select To Compare

Alternative Project Comparisons

Danger 🚫

License Gem CI

Formalize your Pull Request etiquette.

What is Danger?VisionHelping OutPlugin Development

What is Danger?

Danger runs after your CI, automating your team's conventions surrounding code review.

This provides another logical step in your process, through this Danger can help lint your rote tasks in daily code review.

You can use Danger to codify your team's norms, leaving humans to think about harder problems.

For example?

You can:

  • Enforce CHANGELOGs
  • Enforce links to Trello/JIRA in PR/MR bodies
  • Enforce using descriptive labels
  • Look out for common anti-patterns
  • Highlight interesting build artifacts
  • Give specific files extra focus

Danger provides the glue to let you build out the rules specific to your team's culture, offering useful metadata and a comprehensive plugin system to share common issues.

Getting Started

Alright. So, actually, you may be in the wrong place. From here on in, this README is going to be for people who are interested in working on and improving on Danger.

We keep all of the end-user documentation at https://danger.systems.

Some quick links: Guides Index, DSL Reference, Getting Started and What does Danger Do?.

I'm here to help out!

Brilliant. So, let's get you set up.

git clone https://github.com/danger/danger.git
cd danger
bundle install
bundle exec rake spec

This sets everything up and runs all of the tests.


Danger has a VISION.md file, which sums up the ideas around what Danger is. It is the lower bounds of what Danger means. Orta has written on handling and creating Danger on the Artsy blog, too.


The code you write may end up in the public part of the website — the easiest way to tell is that it is vastly overdocumented. If you are working in a space that looks over-documented, please be extra considerate to add documentation. We expect the consumers of that documentation to be non-rubyists, thus you should avoid specific jargon and try to provide duplicate overlapping examples.


So far, we've not really figured out the right way to make tests for our CLI commands. When we have done so, they've ended up being brittle. So, ideally, try to move any logic that would go into a command into separate classes, and test those. We're okay with the command not having coverage, but ideally the classes that make up what it does will.

I'd strongly recommend using bundle exec guard to run your tests as you work. Any changes you make in the lib, or specs will have corresponding tests run instantly.


Ruby is super dynamic. One of the best ways to debug Ruby code is by using pry. We include pry for developers: when you have a problem, copy these two lines just before your problem and follow the instructions from "I Want To Be A Danger Wizard."

require 'pry'

License, Contributor's Guidelines and Code of Conduct

We try to keep as much discussion as possible in GitHub issues, but also have a pretty inactive Slack --- if you'd like an invite, ping @Orta a DM on Twitter with your email. It's mostly interesting if you want to stay on top of Danger without all the emails from GitHub.

This project is open source under the MIT license, which means you have full access to the source code and can modify it to fit your own needs.

This project subscribes to the Moya Contributors Guidelines which TLDR: means we give out push access easily and often.

Contributors subscribe to the Contributor Code of Conduct based on the Contributor Covenant version 1.3.0.

Popular Code Review Projects
Popular Continuous Integration Projects
Popular Software Development Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Code Review