emizzle 5ea4807c90 feat(@embark/pipeline): Add `enabled` property to pipeline config ... Add an `enabled` property to the pipeline config. This lets developers disable the pipeline using the config file. Updates to the enabled property will be reflected while embark is running. For example if embark is running with the pipeline, setting `enabled: false` in the pipeline config will build/deploy the contracts but not run the pipeline. Conversely, if embark is running with the pipeline disabled, enabling the pipeline in the config will build/deploy the contracts then build the dapp.		2019-03-12 07:53:04 -04:00
..
embark	feat(@embark/pipeline): Add `enabled` property to pipeline config	2019-03-12 07:53:04 -04:00
embark-async-wrapper	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
embark-compiler	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
embark-graph	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
embark-reset	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
embark-typings	feat: add repository.directory field to package.json	2019-03-11 18:21:24 -04:00
embark-ui	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
embark-vyper	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
embarkjs	feat: add repository.directory field to package.json	2019-03-11 18:21:24 -04:00
embarkjs-connector-web3	build: use package.json "files" instead of .npmignore	2019-03-12 07:50:25 -04:00
.yarnrc	build: cleanup .yarnrc	2019-02-05 14:15:39 -06:00