Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/workflows/closed-issue-comment.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
name: Closed Issue Comment

This comment was marked as outdated.


on:
issue_comment:
types: [created]

permissions: {}

jobs:
closed-issue-comment:
uses: aws/aws-durable-execution-ci/.github/workflows/closed-issue-comment.yml@e04e810d6d7e452377bbefc04f007ad7373d19e2 # v0.6.0
Comment on lines +10 to +11

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex AI review · Finding arf_v1_fzhse24fidpq6u7qaldkguyzo3

[P2] Supply the required design note for this new feature

Rule 3, “Write a design note before the code,” applies to the new closed-issue notification behavior. The description identifies the shared workflow and pin, but omits the cause, alternatives including simplification of existing notification logic, selection rationale, and what the change removes. This leaves the approach unevaluated under the repository’s rules. Return to the design phase under Rule 8, step 6, and document the required design before proceeding.

To suppress repeats, reply /ai verdict deferred, /ai verdict false-positive, or /ai verdict out-of-scope on the first nonblank line. Add rationale on later lines. A new /ai verdict accepted allows future repeats again.

secrets:
SLACK_WEBHOOK_URL_ISSUE: ${{ secrets.SLACK_WEBHOOK_URL_ISSUE }}
Loading