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

Add an alternative for env.SLACK_WEBHOOK_URL for reusable workflows #234

Closed
sneetsher opened this issue Mar 21, 2022 · 0 comments · Fixed by #242
Closed

Add an alternative for env.SLACK_WEBHOOK_URL for reusable workflows #234

sneetsher opened this issue Mar 21, 2022 · 0 comments · Fixed by #242
Labels
enhancement New feature or request

Comments

@sneetsher
Copy link

Is your feature request related to a problem? Please describe.

I was trying to break down long github workflow using reusable workflow. However, act10ns/slack does only support env.SLACK_WEBHOOK_URL as environment variable while reusable workflow is missing that context and has only inputs & secrets.

Describe the solution you'd like

If possible to have an alternative way to set SLACK_WEBHOOK_URL using secrets which kind of common or through direct parameter with:

Describe alternatives you've considered

Currently, no workaround it. I just keep single file for whole process.

Additional context

No

@sneetsher sneetsher changed the title Add an alternative for env.SLACK_WEBHOOK_URL Add an alternative for env.SLACK_WEBHOOK_URL for reusable workflows Mar 21, 2022
@satterly satterly added the enhancement New feature or request label Jul 1, 2022
satterly added a commit that referenced this issue Jul 1, 2022
satterly added a commit that referenced this issue Jul 2, 2022
satterly added a commit that referenced this issue Jul 2, 2022
satterly added a commit that referenced this issue Jul 2, 2022
satterly added a commit that referenced this issue Jul 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants