The reaction from renovate-tests

reaction's Introduction

::::::::: :::::::::: ::: :::::::: ::::::::::: ::::::::::: :::::::: :::: ::: :+: :+: :+: :+: :+: :+: :+: :+: :+: :+: :+: :+:+: :+: +:+ +:+ +:+ +:+ +:+ +:+ +:+ +:+ +:+ +:+ :+:+:+ +:+ +#++:++#: +#++:++# +#++:++#++: +#+ +#+ +#+ +#+ +:+ +#+ +:+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+#+# #+# #+# #+# #+# #+# #+# #+# #+# #+# #+# #+# #+# #+#+# ### ### ########## ### ### ######## ### ########### ######## ### ####

Installation

$ git clone --recursive https://github.com/artsy/reaction.git
$ cd reaction
$ npm install -g yarn
$ yarn install
$ brew install watchman (If you don't already have Homebrew, go here for installation instructions: https://brew.sh/)
$ cp .env.oss .env

Instructions

Development of components happen in storybooks:

  $ yarn start
  $ open http://localhost:9001/

Run the tests:
```
  $ yarn test
```
Run the tests continuously (or use vscode-jest):
```
  $ yarn test -- --watch
```
In vscode, run the TypeScript: Run type-checker task and open the PROBLEMS view to see continuous type-checker results.
After updating components, be sure to deploy a new demo (sharing is caring!):
```
  $ yarn deploy-storybook
```
When using new changes in metaphysics’ schema, be sure to update the local schema copy:
```
  $ yarn sync-schema
```

There are some suggested VSCode extensions in .vscode/extensions.json and additional docs at docs/vscode.md.

Linking and Unlinking with Force

To link your local reaction with your local force, run:

    $ yarn link && yarn watch
    (wait until you see a message that X files have been successfully compiled before moving on)

    $ cd ../force && yarn link @artsy/reaction && yarn start

To unlink your local reaction from your local force, run (in Force):

    $ yarn unlink @artsy/reaction
    $ yarn add @artsy/reaction
    $ yarn start

Deployments

Reaction uses auto-release to automatically release on every PR. Every PR should have a label that matches one of the following

Version: Trivial
Version: Patch
Version: Minor
Version: Major

Peril will automatically add "Version: Patch", if you don't set one on creating your PR. No release will happen on a Trivial update.

If you're making a change but you don't want to immediate trigger a release (i.e. when 2 PRs need to go out together), specify the correct version and add the Skip Release label. That'll ensure when the next release happens the version is still bumped appropriately.