Yousaf Nabi

Hey @vrknetha @heidi-patrick Sounds like a good idea, I've not had a play with github actions yet, happy for contributions

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?

weird, could you try echoing it out on a step, you might need to export it in your ci runner like `export SLACK_WEBHOOK_URL = ${{ secrets.SLACK_WEBHOOK_TEST_AUTOMATION }}` ?

Just looking at the docs https://docs.github.com/en/actions/reference/encrypted-secrets#using-encrypted-secrets-in-a-workflow ``` steps: - name: Hello world action with: # Set the secret as an input super_secret: ${{ secrets.SuperSecret }} env: # Or as an...

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...

Hey dudes, you probably need to @ tag me otherwise I will miss notifications, thanks for the report. I haven't really looked at my OSS projects this year so apologies....

Hey @HernanMinted If you or someone can provide a reproducible example that would help, otherwise I'm pretty unlikely to sort it until I do a rewrite of the codebase, which...

Hmm, yeah I was going to ask if its only in certain scenarios, as we made a change to support difference webhook urls for failing/passing/build failing messages https://github.com/YOU54F/cypress-slack-reporter/blob/master/src/slack/slack-alert.ts#L115-L126 the problem...

you export them to your shell `export SLACK_WEBHOOK_URL=https://hooks.slack.foo`

where did you paste the code lines?