b149d2a0d6
Summary: Run Danger on all the PRs, not just on the forks, use fail or warning where is needed and make CircleCI fail if danger fails ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://github.com/facebook/react-native/wiki/Changelog --> [Internal] - Run Danger on all the PRs and use fail or warning where is needed. Pull Request resolved: https://github.com/facebook/react-native/pull/33872 Test Plan: Run the change on CirlceCI Reviewed By: cortinico Differential Revision: D36516847 Pulled By: f-meloni fbshipit-source-id: 2c956295a56cc8aa47df4c64f8ca0a211796c73c |
||
---|---|---|
.. | ||
.babelrc | ||
README.md | ||
code-analysis-bot.js | ||
dangerfile.js | ||
datastore.js | ||
make-comment.js | ||
package.json | ||
post-artifacts-link.js | ||
report-bundle-size.js | ||
yarn.lock |
README.md
Danger
Danger is a JavaScript runtime which helps you provide continuous feedback inside GitHub. It's used by @pull-bot to analyze the contents of a GitHub pull request.
If you want to test changes to Danger, I'd recommend checking out an existing PR and then running the danger pr
command.
You'll need a GitHub token. You can re-use this one: a6edf8e8d40ce4e8b11a 150e1341f4dd9c944d2a
(just remove the space).
So, for example:
DANGER_GITHUB_API_TOKEN=[ENV_ABOVE] yarn danger pr https://github.com/facebook/react-native/pull/1234
Code Analysis Bot
The code analysis bot provides lint and other results as inline reviews on GitHub. It runs as part of the Circle CI analysis workflow.
If you want to test changes to the Code Analysis Bot, I'd recommend checking out an existing PR and then running the analyze pr
command.
You'll need a GitHub token. You can re-use this one: 312d354b5c36f082cfe9
07973d757026bdd9f196
(just remove the space).
So, for example:
GITHUB_TOKEN=[ENV_ABOVE] GITHUB_PR_NUMBER=1234 yarn lint-ci