Git push to remote in verbose mode

[llaville]

While, I am always used now the hook:pre-push CapN command to test my hook before to use it in live condition.

Sometimes I forgot it, and I want be to have the same results when I run the following command

git push origin <remote-branch> --dry-run -v

Note

Usage of --dry-run flag here is for test purpose only. The main important condition, is the use of -v (verbose) flag.

Important

The verbosity setting into captainhook.json config file is defined to normal

Current Output

Expected Output

This result is what I got, if I run following command :

vendor/bin/captainhook hook:pre-push -v

Important

The -v flag is provided while the verbosity is still defined to normal in CaptainHook config file.

Actually, if I want the expected result in LIVE mode (git push), I MUST set the verbosity setting to verbose into captainhook.json.

My request is to have the same behavior (LIVE mode and hook:pre-push command) without to change the verbosity setting in CaptainHook config file.

[llaville]

FYI, my current pre-push hook is defined as follow :

[sebastianfeldmann]

So you want the -v command from the original git command to carry over to the hook.

I'm not sure we can do this, because in a hook we do not have access to the original git command only to the hook command that git executes. I will check and see what options we have.

[sebastianfeldmann]

Options I found

1. Wrap the git command in a custom script that somehow stores the command.
2. Use an env variable to trigger verbose output

I think option one is way too invasive and brittle.
We could do something like

CAPTAINHOOK_VERBOSITY=verbose git push --dry-run -v

Not very convenient, but would work.

[llaville]

@sebastianfeldmann Thanks for your reply, but I've found a NICE solution that did not use any new env var !

After trying some solutions, I finally check on one of the project repository I've marked as follow :

• https://github.com/aitemr/awesome-git-hooks

Here are my pre-push modified that include the tips (retrieve the current git command : PUSH_COMMAND=$(ps -ocommand= -p $PPID))

#!/bin/sh

# installed by CaptainHook 5.29.2

INTERACTIVE="--no-interaction"

# if necessary read original hook stdIn to pass it in as --input option
input=$(cat)

if [ -t 1 ]; then
    # If we're in a terminal, redirect stdout and stderr to /dev/tty and
    # read stdin from /dev/tty. Allow interactive mode for CaptainHook.
    exec >/dev/tty 2>/dev/tty </dev/tty
    INTERACTIVE=""
fi

PUSH_COMMAND=$(ps -ocommand= -p $PPID)
VERBOSE="-v"

if [ ! -z "${PUSH_COMMAND##*$VERBOSE*}" ]; then
    VERBOSE=""
fi

vendor/bin/captainhook $INTERACTIVE $VERBOSE --configuration=captainhook.json --bootstrap=autoload.php --input="$input" hook:pre-push "$@"

It works as expected :

tested with -v and --verbose flag

[sebastianfeldmann]

Hacky, but would work ;)

Not sure if I want to add something like that.