Act: Support for $GITHUB_ENV

[haizaar]

Good day,
First, thank you for writing this tool - AFAIK it's the only local simulator for any CI out there.

To the topic - GH seem to have moved to a new way to define env vars [1]:

echo "action_state=yellow" >> $GITHUB_ENV

However it doesn't seem to be supported by act. Specifying the following in the workflow file:

- name: Set CI instance ID                                                                                               
  run: |                                                                                                                 
    echo GITHUB_ENV=$GITHUB_ENV                                                                                          
    echo 'CI_INSTANCE_ID="-ci${{ github.run_id }}"' >> $GITHUB_ENV  

fails with:

| GITHUB_ENV=
| /github/workflow/1: line 3: $GITHUB_ENV: ambiguous redirect

Can you please support it?

[1] https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-commands-for-github-actions#setting-an-environment-variable

[haizaar]

Using the set-env command also results in a deprecation warning:

The `set-env` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

[fd0]

Thank you very much for this great tool! This issue also applies to the add-path command (e.g. via echo ::add-path).

[Jaesin]

Another common use is writing to $GITHUB_PATH. i.e. echo "$(composer config -g home)/vendor/bin" >> $GITHUB_PATH so the path persists in subsequent run steps. $GITHUB_PATH would be a file that would get parsed for paths on every run command. I remember doing something like this manually with travisci a while back so it would be really nice to have this working.

[Risto-Stevcev]

Any updates on this?

[torbjornvatn]

I've gave this a go yesterday, not completely done yet though.
I'll report back when I get it working.

[haizaar]

set-env & friends commands are now disabled by default, i.e. warnings became errors.
Now need to set ACTIONS_ALLOW_UNSECURE_COMMANDS to make it still work.

[torbjornvatn]

@haizaar I'll see if I manage to wrap up my PR on this today

[torbjornvatn]

I have something working now. Just have to do some clean up and testing tomorrow

[haizaar]

@torbjornvatn If you have a build to test, let me know.

[ambientsound]

Any updates here?

[torbjornvatn]

426 is being reviewed by @cplee