We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Due to the use of dockers, my grump config only uses shell tasks , example:
grumphp: process_timeout: 512 tasks: magento_composer: scripts: - ["-c", "/usr/local/bin/composer2 --working-dir=./magento validate"] metadata: task: shell magento_stan-check: scripts: - ["-c", "/usr/local/bin/composer2 --working-dir=./magento stan-check"] metadata: task: shell integrations_composer: scripts: - ["-c", "/usr/local/bin/composer2 --working-dir=./integrations validate"] metadata: task: shell integrations_cs-check: scripts: - ["-c", "/usr/local/bin/composer2 --working-dir=./integrations cs-check"] metadata: task: shell
Most of these tasks start properly when PHP files are changed as per documentation https://github.com/phpro/grumphp/blob/v2.x/doc/tasks/shell.md for triggered_by .
Sadly, the composer validate is not triggered if only composer.json/composer.lock is changed. I can add these:
composer validate
magento_composer: scripts: - ["-c", "/usr/local/bin/composer2 --working-dir=./magento validate"] metadata: task: shell triggered_by: [json, lock]
But that means the task will run even if a non-related json or lock file is changed.
To avoid this, specifying a complete filename should help as in this example:
triggered_by: [composer.lock, composer.json]
or even with wildcards:
triggered_by: [composer.*]
As you can see in my example, I've duplicate tasks but for different folders. The path should be definable too in triggered by, full example:
magento_composer: scripts: - ["-c", "/usr/local/bin/composer2 --working-dir=./magento validate"] metadata: task: shell triggered_by: ['./magento/composer.*']
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Due to the use of dockers, my grump config only uses shell tasks , example:
Most of these tasks start properly when PHP files are changed as per documentation https://github.com/phpro/grumphp/blob/v2.x/doc/tasks/shell.md for triggered_by .
Sadly, the
composer validate
is not triggered if only composer.json/composer.lock is changed. I can add these:But that means the task will run even if a non-related json or lock file is changed.
To avoid this, specifying a complete filename should help as in this example:
or even with wildcards:
As you can see in my example, I've duplicate tasks but for different folders. The path should be definable too in triggered by, full example:
The text was updated successfully, but these errors were encountered: