Question

A build step in your workflow generates a multi-line changelog string that a later step in the same job must read as a single environment variable named CHANGELOG. Your teammate wrote the following and it fails because the runner interprets each line as a separate command: echo "CHANGELOG=$CHANGELOG_TEXT" >> "$GITHUB_ENV". What is the correct way to write a multi-line value to GITHUB_ENV?

Accepted Answer

Use a heredoc-style delimiter, e.g. printf 'CHANGELOG<> "$GITHUB_ENV"

Answer

Replace all newlines with the literal string 
 before echoing the value into $GITHUB_ENV

Answer

Write the value to $GITHUB_OUTPUT instead, since GITHUB_ENV cannot hold more than one line

Answer

Wrap the value in double quotes and set the shell to bash so newlines are preserved automatically