Repository navigation
ci: use DISPATCH_TOKEN for cross-repo dispatch - #22
Merged
Merged
Conversation
The Trigger Dependent Workflows step was using secrets.GITHUB_TOKEN to dispatch events to other repositories. GITHUB_TOKEN is scoped to the current repository and cannot create repository_dispatch events on other repos, resulting in HTTP 403 errors. Switch to secrets.DISPATCH_TOKEN which has the necessary cross-repo permissions, matching the pattern already used by cpython and nanvix/nanvix's publish-release action. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
Trigger Dependent Workflowsstep usessecrets.GITHUB_TOKENto dispatchrepository_dispatchevents to other repositories. However,GITHUB_TOKENis scoped to the current repository and cannot create dispatch events on other repos, resulting in HTTP 403 errors.This switches to
secrets.DISPATCH_TOKENwhich has cross-repo permissions, matching the pattern already used by cpython and nanvix/nanvix's publish-release action.Evidence from workflow logs (nanvix 0.12.104 release):