Adds Danger support
Summary:
Testing Danger support in CI. Continuation of #14964, which Circle stopped building.
Update your node modules first: `npm install`
`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:
```
> react-native@1000.0.0 danger /Users/hramos/git/react-native
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/14951"
{
fails: [],
warnings: [
{
message: ":construction_worker: Work In Progress - <i>Do not merge yet.</i>"
},
{
message: ":lock: Changes were made to package.json - <i>This will require a manual import. Once approved, a Facebook employee should import the PR, then run `yarn add` for any new packages.</i>"
}
],
messages: [],
markdowns: ["This PR requires attention from the facebook/react-native team."]
}
```
`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):
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan</i>"
}
],
messages: [],
markdowns: []
}
```
`npm run danger pr https://github.com/facebook/react-native/pull/13186`
Should warn against a missing test plan:
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan.</i>"
}
],
messages: [],
markdowns: [":page_facing_up: Thanks for your contribution to the docs!"]
}
```
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`
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan.</i>"
}
],
messages: [],
markdowns: ["This PR has been submitted by a core contributor. Notifying facebook/react-native."]
}
```
Closes https://github.com/facebook/react-native/pull/15061
Differential Revision: D5436605
Pulled By: hramos
fbshipit-source-id: 4ba9e812387d8a69893dab537af9b6cd108753cf
2017-07-18 18:08:35 +00:00
/ * *
* Copyright ( c ) 2013 - present , Facebook , Inc .
* All rights reserved .
*
* This source code is licensed under the BSD - style license found in the
* LICENSE file in the root directory of this source tree . An additional grant
* of patent rights can be found in the PATENTS file in the same directory .
* /
'use strict' ;
const fs = require ( 'fs' ) ;
const includes = require ( 'lodash.includes' ) ;
Warn if base !== master, tag CODEOWNERS
Summary:
The following PR modifies the Danger rules in the following way:
1. Verifies if a PR is opened against master. If not, it will warn (if opened against stable) or fail (anything else).
2. No longer adds a markdown message tagging the facebook/react-native team, as the bot does not have the necessary scope to mention the team.
3. Mentions people that have marked themselves as interested in a file, when that file is modified. This is based off CODEOWNERS. The bot should be able to use mentions here as it will act as any other regular user.
Verify it tags the right people in https://github.com/facebook/react-native/pull/15139
```
$ npm run danger pr https://github.com/facebook/react-native/pull/15139
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/15139"
{
fails: [],
warnings: [],
messages: [],
markdowns: ["Attention: grabbou, kureev"]
}
```
It should not tag anyone for https://github.com/facebook/react-native/pull/15175:
```
$ npm run danger pr https://github.com/facebook/react-native/pull/15175
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/15175"
{
fails: [],
warnings: [],
messages: [],
markdowns: []
}
```
It should warn on https://github.com/facebook/react-native/pull/14640 as it targets 0.45-stable:
```
$ npm run danger pr https://github.com/facebook/react-native/pull/14640
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/14640"
{
fails: [],
warnings: [
{
message: ":grey_question: Base Branch - <i>The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The [Releases Guide](https://github.com/facebook/react-native/blob/master/Releases.md) has more information.</i>"
}
],
messages: [],
markdowns: [":page_facing_up: Thanks for your contribution to the docs!"]
}
```
It should not warn on https://github.com/facebook/react-native/pull/15175 because it targets master.
```
$ npm run danger pr https://github.com/facebook/react-native/pull/15175
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/15175"
{
fails: [],
warnings: [],
messages: [],
markdowns: []
}
```
Closes https://github.com/facebook/react-native/pull/15179
Differential Revision: D5490047
Pulled By: hramos
fbshipit-source-id: a46a23b7d0a59d12b8039746d6e9c4399ef32d5f
2017-07-25 19:14:41 +00:00
const minimatch = require ( 'minimatch' ) ;
Adds Danger support
Summary:
Testing Danger support in CI. Continuation of #14964, which Circle stopped building.
Update your node modules first: `npm install`
`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:
```
> react-native@1000.0.0 danger /Users/hramos/git/react-native
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/14951"
{
fails: [],
warnings: [
{
message: ":construction_worker: Work In Progress - <i>Do not merge yet.</i>"
},
{
message: ":lock: Changes were made to package.json - <i>This will require a manual import. Once approved, a Facebook employee should import the PR, then run `yarn add` for any new packages.</i>"
}
],
messages: [],
markdowns: ["This PR requires attention from the facebook/react-native team."]
}
```
`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):
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan</i>"
}
],
messages: [],
markdowns: []
}
```
`npm run danger pr https://github.com/facebook/react-native/pull/13186`
Should warn against a missing test plan:
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan.</i>"
}
],
messages: [],
markdowns: [":page_facing_up: Thanks for your contribution to the docs!"]
}
```
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`
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan.</i>"
}
],
messages: [],
markdowns: ["This PR has been submitted by a core contributor. Notifying facebook/react-native."]
}
```
Closes https://github.com/facebook/react-native/pull/15061
Differential Revision: D5436605
Pulled By: hramos
fbshipit-source-id: 4ba9e812387d8a69893dab537af9b6cd108753cf
2017-07-18 18:08:35 +00:00
import { danger , fail , markdown , warn } from 'danger' ;
const isDocsFile = path => includes ( path , 'docs/' ) ;
const editsDocs = danger . git . modified _files . filter ( isDocsFile ) . length > 0 ;
const addsDocs = danger . git . created _files . filter ( isDocsFile ) . length > 0 ;
if ( addsDocs || editsDocs ) {
// Note, this does not yet cover edits to the autogenerated docs
// (e.g. comments within JS source files)
markdown ( ':page_facing_up: Thanks for your contribution to the docs!' ) ;
}
const isBlogFile = path => includes ( path , 'blog/' ) ;
// Flags new blog posts. Note that mentions will not be parsed as the access token we're using does
// not belong to the Facebook org (on purpose)
const addsBlogPost = danger . git . created _files . filter ( isBlogFile ) . length > 0 ;
if ( addsBlogPost ) {
const message = ':memo: Blog post' ;
const idea = 'This PR appears to add a new blog post, ' +
'and may require further review from the React Native team.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// Flags edits to blog posts
const editsBlogPost = danger . git . modified _files . filter ( isBlogFile ) . length > 0 ;
if ( editsBlogPost ) {
const message = ':memo: Blog post' ;
const idea = 'This PR appears to edit an existing blog post, ' +
'and may require further review from the React Native team.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// Fails if the description is too short.
if ( danger . github . pr . body . length < 10 ) {
fail ( ':grey_question: This pull request needs a description.' ) ;
}
// Warns if the PR title contains [WIP]
const isWIP = includes ( danger . github . pr . title , '[WIP]' ) ;
if ( isWIP ) {
const message = ':construction_worker: Work In Progress' ;
const idea = 'This PR appears to be a work in progress, and may not be ready to be merged yet.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// Warns if there are changes to package.json, and tags the team.
const packageChanged = includes ( danger . git . modified _files , 'package.json' ) ;
if ( packageChanged ) {
const message = ':lock: package.json' ;
const idea = 'Changes were made to package.json. ' +
'This will require a manual import by a Facebook employee.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// Warns if a test plan is missing.
const gettingStartedChanged = includes ( danger . git . modified _files , 'docs/GettingStarted.md' ) ;
const includesTestPlan = danger . github . pr . body . toLowerCase ( ) . includes ( 'test plan' ) ;
// Warns if a test plan is missing, when editing the Getting Started guide. This page needs to be
// tested in all its permutations.
if ( ! includesTestPlan && gettingStartedChanged ) {
const message = ':clipboard: Test Plan' ;
const idea = 'This PR appears to be missing a Test Plan.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// Doc edits rarely require a test plan. We'll trust the reviewer to push back if one is needed.
if ( ! includesTestPlan && ! editsDocs ) {
const message = ':clipboard: Test Plan' ;
const idea = 'This PR appears to be missing a Test Plan.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// Tags PRs that have been submitted by a core contributor.
const taskforce = fs . readFileSync ( '../bots/IssueCommands.txt' , 'utf8' ) . split ( '\n' ) [ 0 ] . split ( ':' ) [ 1 ] ;
const isSubmittedByTaskforce = includes ( taskforce , danger . github . pr . user . login ) ;
if ( isSubmittedByTaskforce ) {
markdown ( 'This PR has been submitted by a core contributor.' ) ;
}
// Warns if the bots whitelist file is updated.
2017-07-19 08:31:44 +00:00
const issueCommandsFileModified = includes ( danger . git . modified _files , 'bots/IssueCommands.txt' ) ;
if ( issueCommandsFileModified ) {
Adds Danger support
Summary:
Testing Danger support in CI. Continuation of #14964, which Circle stopped building.
Update your node modules first: `npm install`
`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:
```
> react-native@1000.0.0 danger /Users/hramos/git/react-native
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/14951"
{
fails: [],
warnings: [
{
message: ":construction_worker: Work In Progress - <i>Do not merge yet.</i>"
},
{
message: ":lock: Changes were made to package.json - <i>This will require a manual import. Once approved, a Facebook employee should import the PR, then run `yarn add` for any new packages.</i>"
}
],
messages: [],
markdowns: ["This PR requires attention from the facebook/react-native team."]
}
```
`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):
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan</i>"
}
],
messages: [],
markdowns: []
}
```
`npm run danger pr https://github.com/facebook/react-native/pull/13186`
Should warn against a missing test plan:
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan.</i>"
}
],
messages: [],
markdowns: [":page_facing_up: Thanks for your contribution to the docs!"]
}
```
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`
```
{
fails: [],
warnings: [
{
message: ":clipboard: Test Plan - <i>This PR appears to be missing a Test Plan.</i>"
}
],
messages: [],
markdowns: ["This PR has been submitted by a core contributor. Notifying facebook/react-native."]
}
```
Closes https://github.com/facebook/react-native/pull/15061
Differential Revision: D5436605
Pulled By: hramos
fbshipit-source-id: 4ba9e812387d8a69893dab537af9b6cd108753cf
2017-07-18 18:08:35 +00:00
const message = ':exclamation: Bots' ;
const idea = 'This PR appears to modify the list of people that may issue commands to the ' +
'GitHub bot.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
Warn if base !== master, tag CODEOWNERS
Summary:
The following PR modifies the Danger rules in the following way:
1. Verifies if a PR is opened against master. If not, it will warn (if opened against stable) or fail (anything else).
2. No longer adds a markdown message tagging the facebook/react-native team, as the bot does not have the necessary scope to mention the team.
3. Mentions people that have marked themselves as interested in a file, when that file is modified. This is based off CODEOWNERS. The bot should be able to use mentions here as it will act as any other regular user.
Verify it tags the right people in https://github.com/facebook/react-native/pull/15139
```
$ npm run danger pr https://github.com/facebook/react-native/pull/15139
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/15139"
{
fails: [],
warnings: [],
messages: [],
markdowns: ["Attention: grabbou, kureev"]
}
```
It should not tag anyone for https://github.com/facebook/react-native/pull/15175:
```
$ npm run danger pr https://github.com/facebook/react-native/pull/15175
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/15175"
{
fails: [],
warnings: [],
messages: [],
markdowns: []
}
```
It should warn on https://github.com/facebook/react-native/pull/14640 as it targets 0.45-stable:
```
$ npm run danger pr https://github.com/facebook/react-native/pull/14640
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/14640"
{
fails: [],
warnings: [
{
message: ":grey_question: Base Branch - <i>The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The [Releases Guide](https://github.com/facebook/react-native/blob/master/Releases.md) has more information.</i>"
}
],
messages: [],
markdowns: [":page_facing_up: Thanks for your contribution to the docs!"]
}
```
It should not warn on https://github.com/facebook/react-native/pull/15175 because it targets master.
```
$ npm run danger pr https://github.com/facebook/react-native/pull/15175
> @ danger /Users/hramos/git/react-native/danger
> node ./node_modules/.bin/danger "pr" "https://github.com/facebook/react-native/pull/15175"
{
fails: [],
warnings: [],
messages: [],
markdowns: []
}
```
Closes https://github.com/facebook/react-native/pull/15179
Differential Revision: D5490047
Pulled By: hramos
fbshipit-source-id: a46a23b7d0a59d12b8039746d6e9c4399ef32d5f
2017-07-25 19:14:41 +00:00
// Warns if the PR is opened against stable, as commits need to be cherry picked and tagged by a release maintainer.
// Fails if the PR is opened against anything other than `master` or `-stable`.
const isMergeRefMaster = danger . github . pr . base . ref === 'master' ;
const isMergeRefStable = danger . github . pr . base . ref . indexOf ( ` -stable ` ) !== - 1 ;
if ( ! isMergeRefMaster && isMergeRefStable ) {
const message = ':grey_question: Base Branch' ;
const idea = 'The base branch for this PR is something other than `master`. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on `master` first and then cherry-pick the commits into the branch for that release. The [Releases Guide](https://github.com/facebook/react-native/blob/master/Releases.md) has more information.' ;
warn ( ` ${ message } - <i> ${ idea } </i> ` ) ;
} else if ( ! isMergeRefMaster && ! isMergeRefStable ) {
const message = ':exclamation: Base Branch' ;
const idea = 'The base branch for this PR is something other than `master`. [Are you sure you want to target something other than the `master` branch?](http://facebook.github.io/react-native/docs/contributing.html#pull-requests)' ;
fail ( ` ${ message } - <i> ${ idea } </i> ` ) ;
}
// People can add themselves to CODEOWNERS in order to be automatically added as reviewers when a file matching a glob pattern is modified. The following will have the bot add a mention in that case.
const codeowners = fs . readFileSync ( '../.github/CODEOWNERS' , 'utf8' ) . split ( '\n' ) ;
let mentions = [ ] ;
codeowners . forEach ( ( codeowner ) => {
const pattern = codeowner . split ( ' ' ) [ 0 ] ;
const owners = codeowner . substring ( pattern . length ) . trim ( ) . split ( ' ' ) ;
const modifiedFileHasOwner = path => minimatch ( path , pattern ) ;
const modifiesOwnedCode = danger . git . modified _files . filter ( modifiedFileHasOwner ) . length > 0 ;
if ( modifiesOwnedCode ) {
mentions = mentions . concat ( owners ) ;
}
} ) ;
const isOwnedCodeModified = mentions . length > 0 ;
if ( isOwnedCodeModified ) {
const uniqueMentions = new Set ( mentions ) ;
markdown ( 'Attention: ' + [ ... uniqueMentions ] . join ( ', ' ) ) ;
}