sourcecred/config
William Chargin f0fcf02791
Check for STOPSHIPs in CI (#301)
Summary:
Placing `STOPSHIP` or `stopship` (or any case variant) in any file
tracked by Git will now cause a `yarn travis` failure. If you need to
use this string, you can concatenate it as `"stop" + "ship"` or
equivalent.

Test Plan:
In `travis.js`, change `"check-stop" + "ships"` to `"check-stopships"`,
and note that this causes the build to fail with a nice message. Note
that this also causes `check-stopships.sh` to fail even when invoked
from an unrelated directory, like `src`.

wchargin-branch: check-stopships
2018-05-25 19:27:31 -07:00
..
jest Ensure that flow is used in all js files (#232) 2018-05-07 20:02:19 -07:00
babel.js Upgrade Flow to v0.72.0 (#285) 2018-05-15 17:09:29 -07:00
env.js Turn on flow for config/env.js (#243) 2018-05-08 14:56:06 -07:00
paths.js Proxy Webpack dev server through to an API server (#245) 2018-05-08 16:09:37 -07:00
polyfills.js Ensure that flow is used in all js files (#232) 2018-05-07 20:02:19 -07:00
travis.js Check for STOPSHIPs in CI (#301) 2018-05-25 19:27:31 -07:00
webpack.config.backend.js Ensure that flow is used in all js files (#232) 2018-05-07 20:02:19 -07:00
webpack.config.dev.js Ensure that flow is used in all js files (#232) 2018-05-07 20:02:19 -07:00
webpack.config.prod.js Ensure that flow is used in all js files (#232) 2018-05-07 20:02:19 -07:00
webpackDevServer.config.js Ensure that flow is used in all js files (#232) 2018-05-07 20:02:19 -07:00