Replies: 3 comments 1 reply
-
|
Nice idea |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Oops actually I'm told it already exists by adding this option: So maybe it would be just nice to have this in the docs! Edit. I would actually be willing to push a PR to update it but I don't quite know where the documentation is located? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The docs can be found in the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Instead of displaying the whole command (written in the

actionkey of each elements of theactionsof a hook), it would be nice to be able to set anameoption that would override this in the CLI output. So instead of this:We could have this:
If actions were configured like this in
captainhook.json:{ "action": "docker compose exec -u sail -T app_laravel npm run lint {$STAGED_FILES|of-type:js}", "name": "lint" }, { "action": "docker compose exec -u sail -T app_laravel vendor/bin/phpstan analyse {$STAGED_FILES|of-type:php}", "name": "phpstan" }, { "action": "docker compose exec -u sail -T app_laravel vendor/bin/php-cs-fixer fix {$STAGED_FILES|of-type:php}", "name": "php-cs-fixer" }What do you think?
Beta Was this translation helpful? Give feedback.
All reactions