Show the stdout from git hooks

[Xapphire13]

It's not uncommon for git hooks to output information as they execute. It would be useful if we could display an output window during the commit phase that mirrored the git commit stdout. This could perhaps be implemented in such a way where it only showed if the stdout was detected to be different for a hook-less commit.

An example of why this is useful:
My team has pre-commit hooks that block a commit that fails linting, in the case where linting fails, the hook prints out the issues to stdout. Using the atom/github package, these messages are hidden.

[BinaryMuse]

@Xapphire13 Do you think it's useful to have this log for successful hook runs as well? Or just failures? And only at the end of committing or also any output obtained during the process (assuming it takes a while)?

[Xapphire13]

For me personally, I care about the failure case. But I think that the most generally applicable fix would be to show stdout for both success and failure.

The issue with this is showing it in a manner that doesn't bother users each time they commit. I can imagine that closing an output window each success will be annoying. Less so if it's only on error.

If there is a way to fit the stdout nicely into the UI without requiring user interaction, that'd be awesome. The only ideas I have right now are:

• A tab for stdout (kinda gross)
• Transition the message/commit box into a stdout text box that remains open in the failure case

[amcvitty]

I'm also having a similar issue, in that the commit hooks take some time to run, and in that time there's no feedback that anything is happening.

Some sort of progress indicator would help show the button has been pressed. Maybe a spinning icon on the commit button.

Edit: just realised that this comment is really a "me too" on issue #929