add info about semaphore and build kite support (#11)

add info about semaphore and build kite support

Author: krzkaczor

README.md

@@ -29,6 +29,7 @@ Expect more docs soon...
 1. [Getting started](getting-started.md)
 1. [How does it work?](how-does-it-work.md)
 1. [Configuration — codechecks.yml/json/ts/js](configuration.md)
+   1. CLI options
 1. [Checks (plugins) development](developing-checks.md)
    1. Developing reusable checks
    1. Testing checks

configuration.md

@@ -81,3 +81,8 @@ It's the same as YML config but written in JSON.
 If you want to execute arbitrary logic this is the way to go. The only thing you need to do is
 export async function from your module. We support es6 named export `main`, default export and
 commonjs export.
+
+## CLI
+
+- `--fail-fast` — stops running checks after the first failure, works only in local mode. CLI exits
+  with non-zero code. This might be useful for executing codechecks in precommit hooks.

supported-ci.md

@@ -2,7 +2,27 @@
 
 - Circle CI
 - Travis CI
+- BuildKite CI
+- Semaphore CI
 
 Is your favorite CI provider missing? Just create an issue
 [here](https://github.com/codechecks/monorepo). You can implement it on your own, read this
 [quick guide](adding-new-ci.md)
+
+## Semaphore CI Known issues
+
+Note that passing secrets requires specifying
+
+```
+secrets:
+  - name: CC_SECRET
+```
+
+in task description.
+
+Unfortunately, at this time Semaphore using codechecks won't have access to detailed PR info (things
+like PR title or body information). It also requires
+[speculative-branch execution](https://github.com/codechecks/docs/blob/master/configuration.md#speculative-branch-execution)
+feature. So please configure branch priority if you use other branches than `master`.
+
+In Semaphore CI settings remember to **turn off** CI execution on pull requests.