ScreamingDev

Use the current discussion in composer and make them take it as "composer/tools" ;-) Perhaps also solving the "require-tools" issue there. https://github.com/composer/composer/issues/9636

Only global scope. Like config files or bootstrapping things. As soon as it is within a lower scope (function, for, if, while, ...) it looses all benefits.

In addition: This should be a suggestion not mandatory. Otherwise code would mix up like ```php const PIE = 3; define( 'WUB', random_int(-PIE,PIE) ); const HELLO = 'World!'; define( 'BYE',...

CI just told me `composer install` after merging via `jq` is the solution for a "dedicated run".

Thanks for your answer. Before I do a fork I need to ask: Has there been a specific reason or problem with feasibility why this is not based on PHPCS?...

commit d57fc619826e8ad1d95e9da7e85a9132d5018035 - Setup presentation

commit 8be427662d62be1eda30f35dd0874ab968116d - Torn presentation in markdown

Hello @celorodovalho . I will add an option to suppress such irrelevant output and/or maybe give the output in some other form (like JSON). In addition I like to update...

Sorry for taking so long to respond. Thank you for letting me know about this problem! Is it within a public repository and can you name the URL to it?...

The tool sourcerer-mike/vcs-protocol can help here.