Allow gatekeeper to be called as reusable workflow#52
Merged
Conversation
pyth-ops
approved these changes
May 11, 2026
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
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.
Summary
workflow_call:trigger toai-gatekeeper.yamlso it can be invoked from wrapper workflows in target repos viauses: pyth-network/shared-actions/.github/workflows/ai-gatekeeper.yaml@main.Why
Required workflows from rulesets only fire on
pull_requestevents, notpull_request_review. Wrapper workflows in target repos can subscribe to both event types and call this reusable workflow, fixing the gap where approvals don't re-trigger the gatekeeper check.Test plan
pull_request/pull_request_reviewtriggers in this repo still work