You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like a better idea to specify task suites in the grumphp configuration.
This way, it is possible a different CI test suite then the pre-commit test-suite.
I was thinking about the following logic:
git:pre-commit uses the git-pre-commit suite if it exists. If it does not exist it used all specified tasks.
git:commit-msg uses the git-commit-essage suite if it exists. If it does not exist it used all specified tasks.
run uses all specified tasks. When a --testsuite=[suite] is specified, the suite is used or an exception is thrown when it does not exist.
When this is implemented, it would be possible to:
Run fast tasks during commit only
Run slower tasks during CI
Run GrumPHP for functional / acceptance tests
Run parts of the tests manually by specifying a testsuite.
For example:
The text was updated successfully, but these errors were encountered: