fix(ci): use pull_request_target for Slack notifications on fork PRs#53
Merged
sabre1041 merged 1 commit intoJul 11, 2026
Merged
Conversation
Fork PRs cannot access repository secrets under pull_request trigger, causing the Slack webhook to fail with 'Missing input' error. Switch to pull_request_target which runs in the base repo context with secret access. Safe because this workflow only sends notifications and does not checkout or execute PR code. Also bumps slack-github-action from v2.1.0 to v2.1.1.
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
pull_requesttopull_request_targettriggerstevefulme1) cannot access repository secrets underpull_request, causingSLACK_WEBHOOK_URLto be empty and the action to fail withMissing input! Either a method or webhook is required to take actionpull_request_targetruns in the base repo context with full secret access — safe here because the workflow only sends notifications and never checks out or executes PR codeslackapi/slack-github-actionfrom v2.1.0 to v2.1.1Evidence
redhat-copbranches (e.g. feat: add cleanup playbooks for migration test environments #51) succeedstevefulme1fork (feat(validate-migration): add post-migration checks #17, feat(mtv-migrate): add warm migration plan support #18, feat(mtv-warm-cutover): add warm migration cutover #19) all fail with identical errorTest plan
redhat-cop-branch PRs still send notifications