Skip to content

feat: add issueComplete notification on issue close#504

Open
MestreY0d4-Uninter wants to merge 1 commit intolaurentenhoor:mainfrom
MestreY0d4-Uninter:feat/issue-complete-notification
Open

feat: add issueComplete notification on issue close#504
MestreY0d4-Uninter wants to merge 1 commit intolaurentenhoor:mainfrom
MestreY0d4-Uninter:feat/issue-complete-notification

Conversation

@MestreY0d4-Uninter
Copy link

Summary

  • Adds new issueComplete notification event type to the NotifyEvent union
  • Adds buildMessage handler for issueComplete with project context and delivery confirmation
  • Emits issueComplete notification in executeCompletion when CLOSE_ISSUE action fires

Motivation

The DevClaw pipeline has notifications for worker start, completion, PR merge, and review routing — but none for the final delivery milestone when an issue is closed. This makes it hard to know when a task has been fully delivered without checking GitHub directly.

Backward compatibility

  • New event type — no breaking changes
  • issueComplete defaults to enabled (like all other event types)
  • Can be suppressed via notifications.issueComplete: false in plugin config

Test plan

  • Build succeeds (npm run build)
  • issueComplete notification fires when tester passes and issue closes
  • Notification content includes project name, issue link, and PR link

Adds a new "issueComplete" notification event type that fires when an issue
is closed via the CLOSE_ISSUE completion action. This provides visibility
into the final delivery milestone of the pipeline.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant