feat(workflows): add closed-PR comment redirect#517
Merged
Conversation
Add closed-pr-comment.yml: detects comments on closed PRs by non-maintainers, posts a redirect to the issue tracker, and pages oncall via the existing SLACK_WEBHOOK_URL. Update slack-issue-notification.yml: switch to injection-safe env+toJSON pattern and emit a uniform 20-key payload (with event_type discriminator) so the Slack workflow can branch on event type. COE AI-7: an external user reported the SDK SPII OTEL leak by commenting on a closed revert PR; oncall does not monitor closed-PR comments, so the report was missed for ~20 hours.
- Gate Slack notification on already_posted so oncall is paged only on the first external comment per PR. Subsequent comments don't page — the redirect comment has already directed the commenter to issues. - Add per-PR concurrency group so the marker-comment dedup is race-free (cancel-in-progress: false to ensure later runs still execute against the just-posted marker). - Inline steps.pr_state.outputs.state in the Slack payload directly rather than routing it through env: to avoid step-level evaluation ambiguity. The value is enum-typed (merged|closed) so injection-safe.
aidandaly24
changed the title
tejaskash
approved these changes
May 21, 2026
Contributor
tejaskash
left a comment
tejaskash
left a comment
There was a problem hiding this comment.
All three prior review comments addressed. LGTM.
… file Address review feedback: - Merge closed-pr-comment.yml and slack-issue-notification.yml into a single github-slack-notifications.yml with two triggers (issues + issue_comment) and two jobs feeding the one shared Slack workflow. - Remove internal incident references from the public workflow. No behavior change: both jobs emit the same 20-key payload the Slack workflow already consumes, gated and deduped exactly as before.
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.
Description
Add a workflow that responds to comments on closed PRs by external users — posts a redirect asking them to open a new issue, and pages oncall via Slack so closed-PR comments are not missed.
Also hardens the existing `slack-issue-notification.yml` to use injection-safe `env:` + `toJSON()` and emits a uniform 20-key payload (with `event_type` discriminator) so the Slack workflow can branch on event type.
Why: COE AI-7 (Bedrock AgentCore SDK SPII OTEL leak). An external user reported the v1.4.8 SPII leak by commenting on a closed revert PR; oncall does not monitor closed-PR comments, so the report was missed for ~20 hours. This closes that detection gap.
Quip: https://quip-amazon.com/SmCwABMBwzgH
Type of Change
Testing
Workflow-only change — no app-code tests apply. Manual test plan once merged:
Open and close a test PR; comment as a non-maintainer; verify bot posts redirect comment AND Slack alert fires.
Comment as a maintainer; verify no redirect, no alert.
Open a real issue; verify existing Slack alert behavior (regression check).
Unit tests pass locally
Integration tests pass (if applicable)
Test coverage remains above 80%
Manual testing completed
Checklist
Security Checklist
Breaking Changes
N/A
Additional Notes
Slack-side change (out of band): The shared Slack workflow `GitHub Issue Response - Moab` was updated separately to add `event_type`/`pr_`/`comment_` variables and branch on event type.