-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
.github/workflows: notify slack for ci-core develop failures #11408
Conversation
I see that you haven't updated any README files. Would it make sense to do so? |
SonarQube Quality Gate |
@@ -29,7 +29,7 @@ jobs: | |||
gc-basic-auth: ${{ secrets.GRAFANA_CLOUD_BASIC_AUTH }} | |||
gc-host: ${{ secrets.GRAFANA_CLOUD_HOST }} | |||
- name: Notify Slack | |||
if: ${{ failure() && github.event.schedule != '' }} | |||
if: ${{ failure() && (github.event_name == 'merge_group' || github.event.branch == 'develop')}} |
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.
Would it be easier to invert this and to instead ignore any pull request events?
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 was worried about including release and master since we sometimes have weird situations there.
Previously, we pushed slack notifications for linter failures and data races for nightly scheduled runs only. This PR expands notifications to all develop and merge queue jobs.