You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
name: Example Set Output
on: [push]
jobs:
example-set-output:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Set an output value
id: step_one
run: echo ::set-output name=FOO::BAR
- name: Display the output value
run: echo The value of FOO is ${{ steps.step_one.outputs.FOO }}
- name: Now try again but with an action
uses: ./.github/workflows/action-set-output
name: Example Action Set Output
description: uses set-output to create a value
runs:
using: "composite"
steps:
- name: Set the value
id: step_one
shell: bash
run: echo ::set-output name=PIE::CAKE
- name: Display the value
shell: bash
run: echo The value of PIE is ${{ steps.step_one.outputs.PIE }}
I didn't even know that this particular feature were broken in act, till I saw your issue and tested it.
there's not been a release since the fix was implemented?
Exactly, if I would be able to create a release I would do it. There are even some votes for a new release #793 (comment) with my changes to composite actions.
System information
act
: ghcr.io/catthehacker/ubuntu:act-latestact
version: 0.2.25Expected behaviour
Using a step like
run: echo ::set-output name=FOO::BAR
in an action should produce a value that is accessible like so:steps.<step id>.outputs.FOO
Actual behaviour
It works for a workflow/job, but not for an action. I have attached an example that should be easy enough to use to reproduce.
The workflow
example-setoutput.yml
and the actionaction-set-output/action.yml
Workflow and/or repository
example.zip
act
outputLog
The text was updated successfully, but these errors were encountered: