Greg Korba

@TomasVotruba please accept workflow, so we can see failed test for recursive merge of skip rules 🙂. Then I'll push the actual fix. PS. Consider allowing workflow runs for all...

No problem, we changed the approach anyway, and define skip rules only in one central config file, so it works properly.

Hi @sebastianbergmann, thanks for reporting the problem. Unfortunately, most probably this is _not_ something we can do on our side, as we utilise [`fidry/cpu-core-counter`](https://github.com/theofidry/cpu-core-counter) which does the CPU auto-detection. We...

It's already in progress in https://github.com/theofidry/cpu-core-counter/pull/127, when this is released, we need to change the usage to utilise new API.

@keradus > I will add more parameters in the future to address the points mentioned above, but they will be added as default parameters hence will not break the API....

Thanks @sebastianbergmann for self-maintenance and the feedback 🍻!

@SpacePossum could you help me with finding points that should be checked out in 7247 and 4502? I find it hard to review this huge change and correlate it with...

@keradus I added unit tests based on eventing system (which I refactored a little, there's no BC-break as all files with changed signature are `@internal`). Without this change it wasn't...

Is it possible to force NeoVim to use `--sequential` flag when running Fixer? Because it does not make sense to use parallel runner in one file's context. Parallel runner shines...

I believe #8154 should fix this, as for 1 file Fixer will always use sequential runner. Please verify it with upcoming release and reopen the issue if problem remains.