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

Error: The set-env command is disabled. #66

Closed
raelriolinozup opened this issue Mar 17, 2021 · 7 comments
Closed

Error: The set-env command is disabled. #66

raelriolinozup opened this issue Mar 17, 2021 · 7 comments

Comments

@raelriolinozup
Copy link

It seems that the outputs are triggering an error on my environment. The Pull Request is actually created, but the action fails when trying to set the outputs. Since i don´t have permission to change my repository config, is it possible to disable this outputs?

Full error message:

Error: Unable to process command '::set-env name=PULL_REQUEST_NUMBER::4' successfully.
Error: The set-env command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Error: Unable to process command '::set-env name=PULL_REQUEST_RETURN_CODE::0' successfully.
Error: The set-env command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Error: Unable to process command '::set-env name=PULL_REQUEST_URL::https://github.com/raelriolinozup/changelog-test/pull/4' successfully.
Error: The set-env command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@vsoch
Copy link
Owner

vsoch commented Mar 17, 2021

We only have that in older versions. What version are you using?

@raelriolinozup
Copy link
Author

I was using version 1.0.6.... But i ended up creating a custom script to post the pull request in node... As a sugestion, maybe it could be a good idea to have an option to toggle the output step for some one else that may face the same issue as mine. =)

@vsoch
Copy link
Owner

vsoch commented Mar 17, 2021

That's an old version - the newer versions don't have this issue. https://github.com/vsoch/pull-request-action/releases/tag/1.0.15. The good idea is to use a more recent version. :)

@flavio-fernandes
Copy link

flavio-fernandes commented Mar 26, 2021

That's an old version - the newer versions don't have this issue. https://github.com/vsoch/pull-request-action/releases/tag/1.0.15. The good idea is to use a more recent version. :)

I think a source for this confusion is because your examples / doc may still be referring to old versions.
Example (line 25 of README.md):

uses: vsoch/pull-request-action@1.0.6

Maybe a way to close this issue is to have them pointing to the latest release.
And THANK YOU for this awesome action!

@vsoch
Copy link
Owner

vsoch commented Mar 26, 2021

That's a great idea! I'll update that to point to master, with a comment to use a specific release. Would that work?

@vsoch
Copy link
Owner

vsoch commented Mar 26, 2021

See #67

@vsoch
Copy link
Owner

vsoch commented Apr 19, 2021

I think this was resolved, closing issue. Thanks again!

@vsoch vsoch closed this as completed Apr 19, 2021
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

3 participants