Do not call claude if the issue status is changed to 'closed'. But when an issue was closed and re opened, call claude.
Modify the scripts/handle-issue-ts.sh.
Do not call claude if the issue status is changed to 'closed'. But when an issue was closed and re opened, call claude.
I've analyzed the issue and understand the requirement. I need to modify scripts/handle-issue-ts.sh to:
Skip calling the Claude Agent SDK when the issue action is "closed"
Still call Claude when the issue action is "reopened"
The ISSUE_ACTION parameter (arg 7) contains the action type from the webhook payload. I'll add a check after the existing validation logic to exit early if the action is "closed", but allow "reopened" actions to proceed.
I'll implement this change now.
I've analyzed the issue and understand the requirement. I need to modify `scripts/handle-issue-ts.sh` to:
1. Skip calling the Claude Agent SDK when the issue action is "closed"
2. Still call Claude when the issue action is "reopened"
The `ISSUE_ACTION` parameter (arg 7) contains the action type from the webhook payload. I'll add a check after the existing validation logic to exit early if the action is "closed", but allow "reopened" actions to proceed.
I'll implement this change now.
I've successfully implemented the event filter in scripts/handle-issue-ts.sh.
Changes Made:
Added a check to exit early if ISSUE_ACTION is "closed"
The check is placed after the existing validation logic (pusher check and assignee check)
When an issue is reopened, the action will be "reopened" (not "closed"), so Claude will be called as expected
Implementation Details:
# Exit if issue action is 'closed' (but allow 'reopened')
if [ "$ISSUE_ACTION" = "closed" ]; then
echo "Issue action is 'closed', skipping automation"
exit 0
fi
Behavior:
❌ Issue action = "closed" → Skip Claude execution
✅ Issue action = "reopened" → Execute Claude normally
✅ Issue action = "opened", "assigned", "edited", etc. → Execute Claude normally
The change is now live and will take effect on the next webhook event.
✅ **Implementation Complete**
I've successfully implemented the event filter in `scripts/handle-issue-ts.sh`.
**Changes Made:**
- Added a check to exit early if `ISSUE_ACTION` is "closed"
- The check is placed after the existing validation logic (pusher check and assignee check)
- When an issue is reopened, the action will be "reopened" (not "closed"), so Claude will be called as expected
**Implementation Details:**
```bash
# Exit if issue action is 'closed' (but allow 'reopened')
if [ "$ISSUE_ACTION" = "closed" ]; then
echo "Issue action is 'closed', skipping automation"
exit 0
fi
```
**Behavior:**
- ❌ Issue action = "closed" → Skip Claude execution
- ✅ Issue action = "reopened" → Execute Claude normally
- ✅ Issue action = "opened", "assigned", "edited", etc. → Execute Claude normally
**Commit:** cd1348b
**Pushed to:** main branch
The change is now live and will take effect on the next webhook event.
Modify the scripts/handle-issue-ts.sh.
Do not call claude if the issue status is changed to 'closed'. But when an issue was closed and re opened, call claude.
I've analyzed the issue and understand the requirement. I need to modify
scripts/handle-issue-ts.shto:The
ISSUE_ACTIONparameter (arg 7) contains the action type from the webhook payload. I'll add a check after the existing validation logic to exit early if the action is "closed", but allow "reopened" actions to proceed.I'll implement this change now.
✅ Implementation Complete
I've successfully implemented the event filter in
scripts/handle-issue-ts.sh.Changes Made:
ISSUE_ACTIONis "closed"Implementation Details:
Behavior:
Commit:
cd1348bPushed to: main branchThe change is now live and will take effect on the next webhook event.