GitHub provides the ACTIONS_STEP_DEBUG setting specifically for increasing the verbosity of workflow step logs. To enable it, create a repository secret or repository variable named ACTIONS_STEP_DEBUG and assign the value true. GitHub states that if both a secret and a variable with this name exist, the secret takes precedence. After the setting is enabled, newly triggered or re-run workflows display additional debugging events in their step logs. Simply defining ACTIONS_STEP_DEBUG under the workflow ' s env or defaults section does not activate GitHub ' s step-debugging mechanism. There is also no supported --actions-step-debug workflow invocation flag. For deeper runner-level diagnostics, GitHub provides the separate ACTIONS_RUNNER_DEBUG setting. Therefore, option C is the documented method for step debug logging.
================
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit