Why does manually invoking lefthook run do nothing until the user presses enter?

[SirzBenjie]

I am using lefthook and I am trying to figure out how to avoid forcing the user to press "enter" before it actually runs the hook.

For example, with this minimal lefthook.yml file:

post-checkout:
  commands:
    foo:
      run: echo foo

When I invoke lefthook from the command line, via lefthook run post-checkout, as an example, after sending the command, the terminal just sits there doing nothing until I press enter a second time.
This means that I can't easily use the command in scripts without forcing a newline to be sent via stdin or something.

This happens even if I pass the --no-tty flag to lefthook run.
Why does this happen, and how do I avoid this?

[mrexox]

This is because of git-lfs post-checkout hook which runs implicitly. You can have a workaround with skip_lfs: true option in the config root

skip_lfs: true

post-checkout:
  …

I will investigate why it freezes

[SirzBenjie]

Any update on the investigation?

[mrexox]

Lefthook tries focusing on implicit flows. In implicit flow you have Git hook controlling STDIN and STDOUT for the lefthook command. LFS is also being run implicitly to address the needs of those who uses LFS without forcing them to configure it.

When running lefthook run manually you control the STDIN, so LFS hook is waiting for some input. I can recommend the following:

1. Use YAML anchors and create another hook with the same commands as in your post-checkout. This way you'll be able to run lefthook run bar instead of lefthook post-checkout but the behavior will be the same

   post-checkout: &post-checkout
     commands: 
       foo:
         run: echo foo
   bar:
     <<: *post-checkout

2. Explicitly disable lfs hooks with skip_lfs: true