Why another echo is needed in custom github action output

Question

From the documentation of github actions:

outputs:
random-number:
  description: "Random number"
  value: ${{ steps.random-number-generator.outputs.random-id }}
runs:
  using: "composite"
  steps:
    - id: random-number-generator
    run: echo "::set-output name=random-id::$(echo $RANDOM)"
    shell: bash

In the run clause 2 echos exist, one for the whole line and one echo $RANDOM

Isn't the second echo unnessecary?

On my computer

echo "::set-output name=random-id::$(echo $RANDOM)"

outputs:

::set-output name=random-id::28124

while

echo "::set-output name=random-id::$RANDOM"

outputs

::set-output name=random-id::28123

so both works.

So why is $(echo $RANDOM) needed ?

who says it's needed?

rethab
– rethab

2022-08-08 07:09:33 +00:00
Commented Aug 8, 2022 at 7:09 — rethab
– rethab, Commented Aug 8, 2022 at 7:09

VonC · Accepted Answer · 2022-08-08 07:59:55Z

1

This comes from Metadata syntax / outputs for composite actions and is not strictly needed.

The documentation mentions:

If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution.

By using $(echo $RANDOM), you "force" said variable substitution.

answered Aug 8, 2022 at 7:59

VonC

1.4m569 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why another echo is needed in custom github action output

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related