StyleCI for better Code-Style

[Gummibeer]

@maknz cause of the fallen keyword "code-style" in PR #44 why not using StyleCI? https://styleci.io/
It's free for open source and also used by laravel core - a simple config could look like:

preset: laravel

risky: false

linting: true

And you can enable auto PR & auto merge & disable CI - this will fix all CS issues in PRs on the fly and no one has to care about CodeStyle.

[soullivaneuh]

Some developer like to fix CS on command line with PHP-CS-Fixer, tools which StyleCI is based.

You can easily provide support for both with this library: https://github.com/Soullivaneuh/php-cs-fixer-styleci-bridge

[soullivaneuh]

And you can enable auto PR & auto merge & disable CI - this will fix all CS issues in PRs on the fly and no one has to care about CodeStyle.

Your choice, but personally 👎 on this. This will produce a lot of PR/commits just for fixing CS and would leave a hard to read history, especially for blame.

[maknz]

StyleCI in general looks good. At the very least it should be red-lighting PRs that have bad code style.

I'll dig into this today.

[soullivaneuh]

@maknz If you are curious, you can see it in action on those projects: https://github.com/sonata-project