Danger Js

⚠️ Stop saying "you forgot to …" in code review
Alternatives To Danger Js
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Reviewdog6,704128a day ago155June 19, 2023114mitGo
🐶 Automated code review tool integrated with any code analysis tools regardless of programming language
Danger5,2231,302682 days ago179June 06, 2023158mitRuby
🚫 Stop saying "you forgot to …" in code review (in Ruby)
Danger Js5,0102,26259811 days ago310July 31, 2023161mitTypeScript
⚠️ Stop saying "you forgot to …" in code review
5 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
24 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 Js
Select To Compare

Alternative Project Comparisons

Formalize your Pull Request etiquette.

What is Danger JS?VisionHelping OutPlugin Development

What is Danger JS?

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

This provides another logical step in your process, through which 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.

Danger JS works with GitHub, BitBucket Server, BitBucket Cloud for code review, then with: Travis CI, GitLab CI, Semaphore, Circle CI, GitHub Actions, Jenkins, Docker Cloud, Bamboo, Bitrise, surf-build, Codeship, Drone, Buildkite, Nevercode, buddybuild, Buddy.works, TeamCity, Visual Studio Team Services, Screwdriver, Concourse, Netlify, CodeBuild, Codefresh, AppCenter, BitBucket Pipelines, Cirrus CI, Codemagic or Xcode Cloud.

npm Build Status Build Status

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 warnings when specific files change

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 JS.

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

Some quick links to get you started:

This thing is broken, I should help improve it!

Awesommmmee. Everything you need is down below. You can also refer to CONTRIBUTING file where you'll find the same information listed below.

git clone https://github.com/danger/danger-js.git
cd danger-js

# if you don't have yarn installed
npm install -g yarn

yarn install

You can then verify your install by running the tests, and the linters:

yarn test
yarn lint

The fixers for both tslint and prettier will be applied when you commit, and on a push your code will be verified that it compiles.

You can run your dev copy of danger against a PR by running:

yarn build; node --inspect distribution/commands/danger-pr.js https://github.com/danger/danger-js/pull/817

How does Danger JS work?

Check the architecture doc.

What is the TODO?

Check the issues, I try and keep my short term perspective there. Long term is in the VISION.md.

Releasing a new version of Danger

Following this commit as a model:

  • Checkout the main branch. Ensure your working tree is clean, and make sure you have the latest changes by running git pull; yarn.
  • Publish - npm run release -- patch --ci.
  • This will trigger a CI run which updates homebrew for the native builds


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 but don't have access to deploy.

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