fix: replace repository-dispatch with direct API call#30060
Merged
Conversation
|
tommasini
approved these changes
May 14, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Description
The
peter-evans/repository-dispatch@v3action is not on the MetaMask org's GitHub Actions allowlist, causing the triage forwarder workflow to fail.Fix
Replace the third-party action with a direct
curlcall to the GitHub REST API (POST /repos/{owner}/{repo}/dispatches). This is consistent with howmetamask-extensiondoes cross-repo dispatch inmain.yml.Changes
peter-evans/repository-dispatch@v3usagecurltohttps://api.github.com/repos/MetaMask/triage-agent/dispatchesjqto match the existingtriage-issueevent contractCHANGELOG entry: null
Pre-merge author checklist
Note
Medium Risk
Changes the
triage-forwarderGitHub Actions workflow dispatch mechanism; a malformed request or auth header could break cross-repo triage dispatching, but scope is limited to automation.Overview
Replaces the
peter-evans/repository-dispatch@v3step in.github/workflows/triage-forwarder.ymlwith a directcurlcall toPOST /repos/MetaMask/triage-agent/dispatchesusing the exchanged installation token.The dispatch payload is now constructed via
jqand sent asevent_type: "triage-issue"with the sameclient_payloadfields as before.Reviewed by Cursor Bugbot for commit 43c8909. Bugbot is set up for automated code reviews on this repo. Configure here.