react-native-macos/bots
Luna Wei 90f0de99ad Remove warning against PR for release branch
Summary:
Changelog: [Internal] Remove warning about creating a pull request to a release branch

We want to support this use case as we want pick requesters to land the cherry-picks themselves and rely on CircleCI automation to test

Reviewed By: cortinico

Differential Revision: D32780819

fbshipit-source-id: 882625a016653dbf480da33fd499d3718b2b5524
2021-12-02 12:11:52 -08:00
..
.babelrc Move danger to bots directory 2018-01-31 16:42:41 -08:00
README.md Add Java linting using google-java-format (#30444) 2020-12-07 03:12:35 -08:00
code-analysis-bot.js JS: Format with Prettier v2.4.1 [3/n] 2021-11-02 22:14:16 -07:00
dangerfile.js Remove warning against PR for release branch 2021-12-02 12:11:52 -08:00
datastore.js OSS CI: Store bundle size info for release branch as well (#32418) 2021-10-18 11:06:33 -07:00
make-comment.js RN: Resolve Outstanding ESLint Warnings 2021-11-09 21:46:21 -08:00
package.json Upgrade to `firebase^9.0.2` in ./bots (#32218) 2021-09-16 13:20:47 -07:00
post-artifacts-link.js ci: ignore bundle size reporter failures (#32490) 2021-11-03 12:10:31 -07:00
report-bundle-size.js ci: ignore bundle size reporter failures (#32490) 2021-11-03 12:10:31 -07:00
yarn.lock Upgrade to `firebase^9.0.2` in ./bots (#32218) 2021-09-16 13:20:47 -07:00

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