[rush] Rush pre/post build hooks should have access the arguments used to call rush build.

[ghost]

We want to use the arguments of our rush build command to modify the behavior of our post build script. However, we have found that these arguments aren't being passed into the post build script's command. Can we change this behavior?

[octogonz]

This is a good idea. Looking at the design of the event hooks, they are shell commands that could already include their own command line parameters.

So perhaps the right design would be to follow the model of Git hooks, and pass the additional information as environment variables.

For example, if you invoke:

rush build --production --verbose

Then perhaps the hook script would get invoked with these variables:

RUSH_HOOK_COMMAND="build"
RUSH_HOOK_COMMAND_PARAMETERS="--production --verbose"

This follows the "Custom Commands" naming conventions.

In the future maybe we would provide other variables.

@iclanton what do you think?