- Notifications
You must be signed in to change notification settings - Fork1k
chore: predicate slack notification job on other jobs#16106
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
always() does not seem to workSigned-off-by: Danny Kopping <danny@coder.com>
-go-race | ||
-go-timing | ||
runs-on:ubuntu-latest | ||
if:always() &&failure() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
always() && failure()
is the same asfailure()
. I think the operative part here is theneeds
section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I mentioned the operative part in the title, although agree this could've been more explicit.
Clause Sonnet suggested thatalways()
could be used if you wanted to handle all jobs (i.e. not have to exhaustively defineneeds
), but maybe that's wrong.
I hate GHA.
dannykopping commentedJan 13, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
f9f72de
intomainUh oh!
There was an error while loading.Please reload this page.
always()
does not seem to workExtending#16105