Support ACTIONS_RUNNER_DEBUG mode about actions

[bigdaz]

Thanks for the interesting idea. I'm not sure that running Gradle with --debug is very useful in general: the amount of logging produced is overwhelming. But running with --info could well be helpful in this case.

Due to the way the action is implemented, it has no direct control over Gradle invocations. Instead, we could detect the presence of ACTIONS_STEP_DEBUG and add this content to ~/.gradle/gradle.properties, which would likely have the desired effect:

org.gradle.logging.level=info
org.gradle.logging.stacktrace=all

[hfhbd]

I want to create a PR if you are okay with it. Do you have a pointer to start?

[bigdaz]

I want to create a PR if you are okay with it. Do you have a pointer to start?

That would be great. You'll likely want to add a new step to initializeGradleUserHome, and add these values to gradle.properties.

A few points:

• You'd need to detect whether gradle.properties already exists, and append if it does.
• I think it's OK to hard-code these values in code: I don't think it's necessary to use a resource file (like we do for init-scripts and toolchains.xml).

There isn't a good guide to contributing, but one hint is you'll need to execute npm run build in order to generate the files into the dist directory.