Ilya Radchenko

That needs to be removed from the README. It's way too outdated.

Any way we could parse out the extra characters introduced once that limit is reached so that readability doesn't suffer?

Have a look at this issue https://github.com/Strider-CD/strider/issues/979 Also which version of Node are you using?

Sounds like a bad install, because `strider-simple-runner` is the default runner and included in the dependencies.

`npm install` was done inside of the strider directory after cloning, otherwise you need to install strider with `npm install -g strider` which would give you a `strider` command in...

@fernandoneto sounds like a nice idea, although not currently supported. You might be able to write a bash script and use it in the custom scripts plugin..

You could use something like [this](http://stackoverflow.com/a/1593574/483616) in a bash if statement in the [strider-custom](https://github.com/Strider-CD/strider-custom)'s (installed by default, enable it in the branches plugins) deploy section.

Ah, so you're wondering if pushing a tag will kick off a job in strider? Not sure.. But using that SO answer you can increment a version somewhere and tag...

Sounds like a feature for strider-github, strider-bitbucket and strider-gitlab

https://developer.github.com/webhooks/#events https://github.com/Strider-CD/strider-github/blob/master/lib/api.js#L42 https://github.com/Strider-CD/strider-github/blob/master/lib/webhooks.js#L227 Add the `create` and `release` events to handle tags and releases. The only issue is how do you decide which branch to trigger? Maybe postfix the tags...