Show live pre-commit/pre-push hook output during commit/push

[remy90]

I sometimes run slow Git hooks (especially pre-push, occasionally pre-commit).
Right now in Lazygit I only see a spinner/status while the operation runs:

When hooks take a while, I often switch to the terminal and run Git directly just to see what stage the hook is in (linting, typecheck, tests, etc.):

Would maintainers be open to a contribution that shows hook output live during commit/push (opt-in), so users can monitor progress without leaving Lazygit?

My intent would be:

• default behavior unchanged
• optional (opt in) config toggle
• generic support for different hook runners (Husky, pre-commit, custom scripts)

If this sounds aligned with Lazygit’s direction, I’d be happy to open a PR.

[remy90]

@stefanhaller any thoughts? Happy to provide more information on the problem if my proposal isn't sufficiently clear

[stefanhaller]

Lazygit shows the output of hooks in the Log panel. At least for pre-commit and pre-push; those are the ones I am using myself. If there are other hooks for which the output doesn't appear in the Log panel, that would be a bug and should be fixed.

There are several problems with using the Log panel for hook output:

• some people hide the Log panel by default. I'm one of them, and judging from your screenshot above, so are you. So you have to type @, enter if you want to see the output. I do this myself when I need to, and find it acceptable.
• some people have hooks that produce so much output that the Log panel's default height of 8 lines is not enough to show it. Those people have to type @, f to make it full screen. (Or, if the small Log panel is already showing, click into it to expand it.)
• there is currently no good way to copy multi-line text from the Log panel to the clipboard. This is not specific to hooks though, and would be a general, independent feature request.

So for my feeling there's nothing to do here, but I'm happy to discuss it more.

Related issues: #3717, #4981

generic support for different hook runners (Husky, pre-commit, custom scripts)

I don't understand this point; what does the way you manage your hooks have to do with where the output goes?