Commit 6889a79
authored
ci(rust): Run CI against toolchain update bot PRs (#2779)
The PRs from the Rust toolchain update bot don't trigger the
`pull_request`-triggered workflows. This is a [GitHub feature, not a
bug.](https://docs.github.com/en/actions/concepts/security/github_token?utm_source=chatgpt.com#when-github_token-triggers-workflow-runs)
This change adds a `workflow_dispatch` trigger to our CI action, and has
the Rust toolchain update bot automatically trigger the action after
opening the PR.
I tested this change with #2781. Although the workflow run does not show
on that PR, we can see that, in fact, the [CI did
run](https://github.com/getsentry/sentry-cli/actions/runs/17911030223)
against the commit. My guess is maybe it has to do with the fact that
the #2781 is against #2780, rather than the `master` branch.1 parent 8db571b commit 6889a79
2 files changed
+12
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| 12 | + | |
| 13 | + | |
12 | 14 | | |
13 | 15 | | |
14 | 16 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
| 16 | + | |
16 | 17 | | |
17 | 18 | | |
18 | 19 | | |
| |||
127 | 128 | | |
128 | 129 | | |
129 | 130 | | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
0 commit comments