You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried to use this action from a self-hosted runner (both runners that are connected to a single repository as well as organization-wide runners) that must use a web proxy for communicating with the internet, in this case the Slack webhook URLs for sending notifications.
It looks like this action does not have support for sending Slack notifications via a web proxy. There are no settings for providing proxy settings. Neither does this action have support for reading the standard proxy environment variables (http_proxy, https_proxy).
Are you planning to implement support for communication via web proxy?
The text was updated successfully, but these errors were encountered:
Hello and welcome to RavSam 💜. Thanks for opening your first issue. I will assign one of our team members to take a look at the problem you have raised. Make sure to include as much information as possible to help our team diagnose the issue and solve it quickly.
If the problem is related to a security concern, then please delete this issue and send us an email at [email protected].
I have tried to use this action from a self-hosted runner (both runners that are connected to a single repository as well as organization-wide runners) that must use a web proxy for communicating with the internet, in this case the Slack webhook URLs for sending notifications.
It looks like this action does not have support for sending Slack notifications via a web proxy. There are no settings for providing proxy settings. Neither does this action have support for reading the standard proxy environment variables (http_proxy, https_proxy).
Are you planning to implement support for communication via web proxy?
The text was updated successfully, but these errors were encountered: