Commit 285990b
authored
ci: forward CUOPT_SLACK_MENTION_ID secret to nightly-summary (#1182)
## Summary
- Declare `CUOPT_SLACK_MENTION_ID` as an optional `workflow_call` secret
on the reusable `nightly-summary` workflow and forward it to the
run-step env.
- Pass it from `test.yaml` to the `nightly-summary` job alongside the
other Slack secrets.
## Why
`ci/nightly_summary.sh` already forwards `CUOPT_SLACK_MENTION_ID` to
`ci/utils/generate_slack_payloads.py`, which uses it to prefix `<@id>`
mentions on **new failures** and **new flaky tests**. Until now the env
var was never populated in CI, so the mention was always empty. With
this change, setting the `CUOPT_SLACK_MENTION_ID` repo secret (Slack
user ID like `U01ABCDEF` or group handle like `S01ABCDEF`) will ping the
configured handle. Leaving it unset preserves the no-mention default.
## Test plan
- [ ] Add `CUOPT_SLACK_MENTION_ID` repo secret.
- [ ] Trigger a nightly run (or `workflow_dispatch` on
`nightly-summary`) and confirm the Slack message includes the `<@id>`
mention on new failures.
- [ ] Verify behavior is unchanged when the secret is unset (no
mention).1 parent 733a459 commit 285990b
2 files changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
| 52 | + | |
| 53 | + | |
52 | 54 | | |
53 | 55 | | |
54 | 56 | | |
| |||
70 | 72 | | |
71 | 73 | | |
72 | 74 | | |
| 75 | + | |
73 | 76 | | |
74 | 77 | | |
75 | 78 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
123 | 123 | | |
124 | 124 | | |
125 | 125 | | |
| 126 | + | |
0 commit comments