Skip to content

test action with PR trigger and older Rust version#2780

Closed
szokeasaurusrex wants to merge 2 commits intoszokeasaurusrex/rust-toolchain-update-ci-workflowfrom
szokeasaurusrex/test-update-toolchain-action
Closed

test action with PR trigger and older Rust version#2780
szokeasaurusrex wants to merge 2 commits intoszokeasaurusrex/rust-toolchain-update-ci-workflowfrom
szokeasaurusrex/test-update-toolchain-action

Conversation

@szokeasaurusrex
Copy link
Copy Markdown
Member

No description provided.

@szokeasaurusrex szokeasaurusrex force-pushed the szokeasaurusrex/rust-toolchain-update-ci-workflow branch from 99aacaa to 2ff1d15 Compare September 22, 2025 09:41
szokeasaurusrex added a commit that referenced this pull request Sep 22, 2025
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant