Skip to content
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

feat: add support for writing to GITHUB_OUTPUT file #181

Merged
merged 1 commit into from
Oct 16, 2022

Conversation

jackton1
Copy link
Member

@jackton1 jackton1 commented Oct 16, 2022

@jackton1 jackton1 merged commit b90df97 into main Oct 16, 2022
@jackton1 jackton1 deleted the feat/add-support-for-writing-to-GITHUB_OUTPUT-file branch October 16, 2022 04:47

echo "::set-output name=ref_branch::$(eval printf "%s" "$REF_BRANCH")"

if [[ -z "$GITHUB_OUTPUT" ]]; then
Copy link

@liljack liljack Feb 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jackton1 Hi,

Thank you for keeping this Github action updated. I was actually looking at the code to see if this action would give me the warnings or if it has been updated to use the new syntax. I looked at the code and came across this.

I was just curious, what does [[ -z "$GITHUB_OUTPUT" ]]do ? never seen this syntax before. (have done very little bash scripting)

Thanks!

Copy link

@thtliife thtliife Aug 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[[ -z "$GITHUB_OUTPUT" ]] is a test for whether the environment variable $GITHUB_OUTPUT is unset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Usage of set-output triggers warnings during workflow.
3 participants