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

Migrate workflows from deprecated 'set-env' and 'add-path' to 'exportVariable' and 'addPath' #1096

Closed
matthewfeickert opened this issue Oct 9, 2020 · 2 comments · Fixed by #1139
Assignees
Labels
CI CI systems, GitHub Actions fix A bug fix

Comments

@matthewfeickert
Copy link
Member

matthewfeickert commented Oct 9, 2020

Description

GitHub Actions is deprecating the set-env and add-path commands in favor of environmental files with the new exportVariable and addPath commands.

Action and workflow authors who are setting environment variables via stdout should update any usage of the set-env and add-path workflow commands to use the new environment files.

The tag workflow currently relies on set-env and so will need to be migrated.

@matthewfeickert matthewfeickert added CI CI systems, GitHub Actions fix A bug fix labels Oct 9, 2020
@matthewfeickert matthewfeickert self-assigned this Oct 9, 2020
@matthewfeickert
Copy link
Member Author

So, seems this can get replaced largely by

echo "{name}={value}" >> $GITHUB_ENV

@matthewfeickert
Copy link
Member Author

(For reference I'm trying to debug the new workflow here https://github.com/matthewfeickert/throw-it-away-now)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI CI systems, GitHub Actions fix A bug fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants