Bart Reunes

@wickedyoda There you go: https://docs.docker.com/compose/compose-file/#compose-file

It would still need to be able to use docker-compose.yaml after the change as well, as it is still supported. And yeah, it is a recent change, they're moving to...

It seems this is not possible anymore, since the `ARG RUBY_VERSION` in the new Dockerfile has no default value.

I have the exact same error trace (same files and lines), but with a different unexpected token. I'm not uploading any files, but I'm not sure what is going wrong...

Thanks for looking into this. I have been playing around a bit with the script. > About the --src, I think you can use absolute paths, its not a problem....

Might be It's because I'm trying to do a `composer global require`, but using it on the local project. I'll try to make a minimal reproducable case.

When you do ``` php run.php --src ./src ``` it is running phpcheckstyle on the src directory inside the phpcheckstyle directory. However, the src I was referring to is the...

Ah, I see. I double checked my initial post, and I failed to mention something quite important: I'm installing phpcheckstyle as a global dependency. I'm using `composer global require --dev...

Just to be sure: did you also remove phpcheckstyle from the local vendor directory after requiring it globally? I added a `var_dump(get_included_files())` in the run.php file, to check which `autoload.php`...

Strange that it found the autoload file, don't know what might be the difference then. Should I be testing against the master branch or the latest release commit 21ceb84ee9f8679eed4c66d210ad3f68f5b22d54?