Valentin Kiselev

Hey! Have you considered using [`env`](https://lefthook.dev/configuration/env.html) option? I think manually adding such envs is better because you don't rely on the tool's implicit behavior.

Hey @SamSaffron, I've prepared the update https://github.com/evilmartians/lefthook/pull/1185, so it adds `text/x-ruby`, but it will work only for scripts with shebang like `#!/usr/bin/env ruby`. What you ask for is to filter...

@SamSaffron filters are reducing the scope, so in your case adding both `glob` and `file_types` will work just like if `filte_type` is added (which is more restrictive I guess). But...

Hey! There's a [`follow`](https://lefthook.dev/configuration/follow.html) option which may help you. You can configure it per-hook ```yml pre-commit: follow: true jobs: - ... ```

Oh, I guess it's the escaping issue with quotes 🤔 Windows behave not like *nix and doesn't allow single quotes. Thank you for creating this bug, I'll try finding the...

Hey! Thank you for sharing the problem. Does the issue only reproduce when you commit from a GUI app? Have you tried the [`rc`](https://lefthook.dev/configuration/rc.html) option?

@ianzone , could you share the use case? Do you need an ability to continue some of the jobs while breaking the pipeline on others?

@ianzone , that’s the default behavior if you don’t specify `piped: true` option. Maybe without a message, but there’s a [`fail_text`](https://lefthook.dev/configuration/fail_text.html) option for that. Do you have `piped: true` in...

Oh, I see, so I think the [workaround](https://github.com/evilmartians/lefthook/issues/1051#issuecomment-3015705813) can be used now. I will consider this feature. It’s exiting with code 0 even if the job failed.

Thank you for creating an issue! I'll consider your suggested options and will come back :+1: