-
Notifications
You must be signed in to change notification settings - Fork 79
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
Env var GITHUB_ACTION is not defined. Maybe try to set it if you are running the script manually. #39
Comments
Seeing the same, probably caused by actions/runner#635 |
Looks like an issue on GitHub's end. I'll deploy a quick fix until they solve this. |
Fix is pushed. Bumped as a minor semver release from 0.1.0 to 0.2.0 (see here why). To fix your pipeline, check sure the version you use is at least I'll have a close look on GitHub's behavior concerning this issue. Thank you. |
There's currently an issue the current version of github's runners that's causing GITHUB_ACTION to be unset which in turn causes problems for Ilshidur/action-discord@master, leading to failed builds See Ilshidur/action-discord#39 and actions/runner#635
There's currently an issue the current version of github's runners that's causing GITHUB_ACTION to be unset which in turn causes problems for Ilshidur/action-discord@master, leading to failed builds See Ilshidur/action-discord#39 and actions/runner#635
@Ilshidur Lovely, thank you for the quick turn around! I was just about to disable discord notifications on my project until Github fixes this on their end, but you just made that unnecessary. Thank you for your awesome work! |
Thank you for your the link your provided. It made it clearly quicker to fix ! I'll be closing this issue. Feel free to comment below in case anything goes wrong again. |
https://github.com/bluelovers/ws-segment/runs/943356195?check_suite_focus=true
The text was updated successfully, but these errors were encountered: