microsoft
/
react-native-macos
зеркало из https://github.com/microsoft/react-native-macos.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
react-native-macos/bots
История
Tom Underhill f52e69bdb2
Fix macOS Alert API issues (#355) 
* Update scripts to publish react-native-macos-init

* Clean up merge markers

* Restored ios:macos RNTester parity except for InputAccessoryView.

* Revert "Restored ios:macos RNTester parity except for InputAccessoryView."

This reverts commit 5a67ae06b0.

* Remove unnecessary android builds and tar file upload.

* Fix macOS alerts and prompts: alert was always showing an edit box, prompt was doing nothing.

* Fixed prompt default value.  linted the JS.   Fixed callbacks in mac native.

* Updated the dangerfile.js to allow macos in the changelog category

Co-authored-by: React-Native Bot <53619745+rnbot@users.noreply.github.com>
 		2020-05-11 16:24:12 -07:00
..
.babelrc Move danger to bots directory 2018-01-31 16:42:41 -08:00
README.md Merge react-native 0.61-stable (#323) 2020-04-28 11:49:15 -07:00
code-analysis-bot.js Merge react-native 0.61-stable (#323) 2020-04-28 11:49:15 -07:00
dangerfile.js Fix macOS Alert API issues (#355) 2020-05-11 16:24:12 -07:00
package.json Merge react-native 0.61-stable (#323) 2020-04-28 11:49:15 -07:00
yarn.lock Merge react-native 0.61-stable (#323) 2020-04-28 11:49:15 -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: 78a72af35445ca3f8180 b1a98e0bbd56ff1ccba1 (just remove the space). So, for example:

GITHUB_TOKEN=[ENV_ABOVE] GITHUB_PR_NUMBER=1234 yarn lint-ci