Skip to content

ACTIONS_RUNNER_PRINT_LOG_TO_STDOUT should be described with example usage  #25041

@mcarans

Description

@mcarans

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions

What part(s) of the article would you like to see updated?

ACTIONS_RUNNER_PRINT_LOG_TO_STDOUT is not documented in the GitHub Actions documentation and should be clearly described along with examples of how and where to set it. If jobs.<job_id>.environment is the correct place to set it, then it should be added there. If not, then it should be added in the appropriate article and place.

From actions/runner#891 (comment), "As of v2.300.0, setting ACTIONS_RUNNER_PRINT_LOG_TO_STDOUT to 1 or true will also print the logs to stdout in addition to the logfile."

ACTIONS_RUNNER_PRINT_LOG_TO_STDOUT may be something that supports the use cases described by many users in the following issues: actions/runner#886, actions/runner#891, actions/runner#2131 and the following discussions: https://github.com/orgs/community/discussions/35363, https://github.com/orgs/community/discussions/44250. Without documentation of ACTIONS_RUNNER_PRINT_LOG_TO_STDOUT, it's hard to know what it is meant to do, what exactly it will output or how to use it.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    actionsThis issue or pull request should be reviewed by the docs actions teamcontentThis issue or pull request belongs to the Docs Content teamneeds SMEThis proposal needs review from a subject matter expertwaiting for reviewIssue/PR is waiting for a writer's review

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions