Add a reusable status_embed workflow#17
Conversation
shtlrs
changed the title
| uses: SebastiaanZ/github-status-embed-for-discord@v0.2.1 | ||
| with: | ||
| # Our GitHub Actions webhook | ||
| webhook_id: '784184528997842985' |
There was a problem hiding this comment.
This should be an input, so the caller can determine what channel it gets sent to
There was a problem hiding this comment.
I think setting it as a variable is better, that way we'd avoid having the with statements scattered all over the over workflows that'll call this one.
At worst, we can have it as an input, and default to the variable. But shouldn't be needed in our case
| # | ||
| # 3. If any workflow ends in failure or was cancelled. | ||
| if: >- | ||
| (github.workflow == 'Deploy' && ${{ inputs.job_status }} != 'skipped') || |
There was a problem hiding this comment.
The Deploy name here won't be the same on all repos. We should make this an input, or standardise the name across our repos as part of the work to use this.
There was a problem hiding this comment.
How about we go for the standardization option?
|
Unfortunately, this won't work out currently due to how contexts are passed from forks. |
2 participants
As a continuation to this PR, we now want all of our repositories that need the
status_embedworkflow to use a centralized reusable workflow.We've decided to add it to this repo and have it referenced by all of our other repositories that need to trigger it upon linting, building, etc.
NOTE
the
GHA_WEBHOOK_TOKENsecret needs to be part of this repository in order for it to be reusable all over.