-
Notifications
You must be signed in to change notification settings - Fork 46
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
Support for github actions #980
Comments
+1 would be great |
Sounds like a good idea, I've not had a play with github actions yet, happy for contributions |
I would love github actions support too. I did test it just to see what happens:
and Erroring I guess because it cannot fetch the webhook URL:
|
Hey @bennymeade, thanks for taking a look! How do env vars get set, the script is using PROCESS.env. Are the github secrets automatically set an env vars in the runner? |
Yes I believe so, in a GH Actions workflow the synatx for calling a secret is like this: ... and it behaves the same as an global variable. |
weird, could you try echoing it out on a step, you might need to export it in your ci runner like
|
|
Just looking at the docs https://docs.github.com/en/actions/reference/encrypted-secrets#using-encrypted-secrets-in-a-workflow
So I think you will need something like
|
Result my mate! How would you feel about sticking something in the readme to cover that for other github actions users, and maybe we can follow this up with a later ticket to support it as a supported |
Yes definitely, I'm happy to do that @YOU54F Thanks again for your speedy responses. |
Here's my GH workflow for others benefit:
with minimalist repo sample here: https://github.com/bennymeade/cypress-slack-reporter-gh-actions |
Hi @bennymeade, I followed your example and got it to work. Thanks for that!
I need to pass But the issue is I have to use a command like this:
Otherwise, the commit link would have duplicated owners. |
Send the message support for Github actions and bitbucket pipelines
The text was updated successfully, but these errors were encountered: