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
This is a git thing and not directly related to this extension, but is there a solution to the problem where git hooks only output to stdout if there is an error that results in exit code of non-zero?
The problem is that we can't show progress in a hook to the git console with echo (or in my case with NodeJS with console.log()) unless we exit with an error. If a hook proceeds to return with code 0 then it suppresses the output.
I'm wondering if there is a way for this extension to capture output to stdout and output that rather than allowing git console output to completely control stdout.
What about optionally injecting GIT_TRACE into the git command lines?
GIT_TRACE=1 git commit
The text was updated successfully, but these errors were encountered:
This is a git thing and not directly related to this extension, but is there a solution to the problem where git hooks only output to stdout if there is an error that results in exit code of non-zero?
The problem is that we can't show progress in a hook to the git console with echo (or in my case with NodeJS with console.log()) unless we exit with an error. If a hook proceeds to return with code 0 then it suppresses the output.
I'm wondering if there is a way for this extension to capture output to stdout and output that rather than allowing git console output to completely control stdout.
What about optionally injecting GIT_TRACE into the git command lines?
GIT_TRACE=1 git commit
The text was updated successfully, but these errors were encountered: