-
Notifications
You must be signed in to change notification settings - Fork 59.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify how multiline output values can be set via GITHUB_OUTPUT
#21529
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@fingolfin Thanks so much for opening an issue! I'll triage this for the team to take a look 👀 |
Thanks for this issue! You or anyone else is welcome to open a PR to point users to the multi-line strings section from the setting an output parameter section. I would recommend including a link instead of referring to "the previous section" to help users find the info even if the structure of this article changes in the future. I think it could also be useful to include an example. |
Hi can I work on this? |
This comment was marked as spam.
This comment was marked as spam.
Summary should use the multiline format: github/docs#21529
* `mimir-rules-action`: `set-output` is deprecated See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ `set-output` will stop working on June 1st and is currently warning * Update entrypoint.sh * Correctly output multiline Summary should use the multiline format: github/docs#21529 * Use `ENDOFSUMMARY` instead of EOF
Struggling with multiline environment variables See github/docs#21529 See #1971
Turns out you can't shove multiline strings into GITHUB_OUTPUT without heredoc syntax. github/docs#21529 Signed-off-by: David Zager <[email protected]>
Turns out you can't shove multiline strings into GITHUB_OUTPUT without heredoc syntax. github/docs#21529 Signed-off-by: David Zager <[email protected]>
Fixing the post processing of label analysis failure based on POC runs (see https://github.com/giovanni-guidini/components-demo/actions/runs/6579967512/job/17876943612 for the end result) The strange syntax came from github/docs#21529 Also letting label-analysis step fail (_after_ the post processing)
Following github/docs#21529
Thank you!!! |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter
What part(s) of the article would you like to see updated?
Due to recent changes, I had to switch our codeflows from using
set-output
to the method described in the section on "Setting an output parameter", by appending to (the file with the name in the variable)$GITHUB_OUTPUT
.This is very similar to how
$GITHUB_ENV
works in the previous section.I had need to post a multiline output, and so decided to just try the technique described for "Environment files" (the preceding section). That is, I used the pattern
and ended up with code looking like this:
And as far as I can tell, this worked great (and is much simpler than what I had to do before).
I think it would be beneficial if this possibility was pointed out by the documentation. Simply saying something akin to "multi-line output values can be set with the same technique used in the previous section to define multi-line environment variables" would already help a lot.
Additional information
No response
edited by maintainer
Content plan here
The text was updated successfully, but these errors were encountered: