GrumPHP VS drupal-project

GrumPHP: A PHP code-quality tool.

Depends on what you mean by plugin, but a GrumPHP is a great tool. It registers a pre-commit git hook that runs whatever quality tools you've configured every time someone commits. If one of the checks fail, the commit is aborted. It's very easy to install and configure.

sounds like you heard of Grumphp

Of course, in this simple way, you will need run the command before commits to ensure a correct code style. We can improve this we can to use some pre-commit hook, like a grumphp https://github.com/phpro/grumphp.

How does this compare to existing tools like GrumPHP or Captain Hook? Why should I use it instead?

Are you aware of GrumPHP?

I use grumphp to run phplint, phpstan, Easy coding standard (includes php-cs fixer) and phpunit. All four will automatically run before every commit, stopping any 'below standard' code from being committed. Example config file

like valplet said: https://github.com/phpro/grumphp But also: https://styleci.io/ integrates nicely with git For client side code formatting check: https://prettier.io/

1) increasing timeout to 6000 as per https://github.com/drupal-composer/drupal-project/issues/197

Check out typical .gitignore files for Drupal. Like https://github.com/drupal-composer/drupal-project/blob/9.x/.gitignore

IF, you are using composer on your deployment targets… The only thing you need to store in git is your composer.json and composer.lock files, AND the /modules/custom/ directory and /themes/custom/ directory. (There’s some other tangentel files, like .gitignore and some other stuff you want in GIT, but it’s a MUCH smaller repository, since you don’t need to move around ALL of the files. Are you using something like this : https://github.com/drupal-composer/drupal-project ?

To update the Drupal core, it is slightly different than the Composer template for Drupal projects way to go, if you are used to it.