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

Using a soon to be deprecated GitHub Actions feature #517

Closed
tevoinea opened this issue Oct 6, 2020 · 1 comment
Closed

Using a soon to be deprecated GitHub Actions feature #517

tevoinea opened this issue Oct 6, 2020 · 1 comment

Comments

@tevoinea
Copy link

tevoinea commented Oct 6, 2020

GitHub Actions is deprecating the set-env and add-path commands. More details here: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

This project uses set-env here:

if ($env:GITHUB_ACTIONS) {
Write-Host "::set-env name=$($_.Key)::$($_.Value)"
}

and add-path here:

if ($env:GITHUB_ACTIONS) {
Write-Host "::add-path::$_"
}

Right now this is causing warnings in all of our workflows that use dotnet and it looks like the Actions team is planning to disable the commands in the future.

The fix seems to be relatively small/easy (the only usages I found were quoted above), if that's the case I'm also happy to open a PR with the fix 😊

@AArnott
Copy link
Collaborator

AArnott commented Oct 6, 2020

Already fixed by #516

@AArnott AArnott closed this as completed Oct 6, 2020
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

No branches or pull requests

2 participants