Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing Danger support in CI. Continuation of #14953, which Circle stopped building.
Test Plan
Update your node modules first:
npm install
Test WIP, package.json warnings
npm run danger pr https://github.com/facebook/react-native/pull/14951
Verify output. This PR should trigger a WIP warning, as well as a package.json warning:
Test plan warnings
npm run danger pr https://github.com/facebook/react-native/pull/14946
Verify output. This PR should trigger a warning against the lack of a test plan (note that the PR does have a test plan, but it does not title it as such):
Warn when a change to the Getting Started guide is missing a test plan
npm run danger pr https://github.com/facebook/react-native/pull/13186
Should warn against a missing test plan:
Flag PRs by core contributors
If the author is able to issue bot commands, we reasonably assume that this is coming from an established core contributor. Their PRs will be flagged for expedited review:
npm run danger pr https://github.com/facebook/react-native/pull/14895