Cancel dispatched events on label change #275

Open
opened 2026-11-13 14:06:34 +01:00 by lucas · 0 comments
Owner

Setting the "ignored" label should cancel a pending or ongoing action.

When creating PRs or issues, setting a label always comes after the creation event. Even if I set the label in the creation dialog, it's still two webhook events in the end. First "issue created" then "label set".
Therefore omp-deck always triggers, and doesn't honor the label, because the event for it arrives afterwards.

So a mechanism is needed where setting a label instructs the dispatcher to cancel. Even ongoing turns should be cancelled sometimes. This would cover both the case where I set the label during creation (the label event should arrive moments after the creation event) or when I forget and set later.

I think for the second case, a small distinction is needed: automated actions, like "triage label applied", "review all PRs", etc. should be cancelled, while direct user interactions (reply to comment, @mention) probably shouldn't

Setting the "ignored" label should cancel a pending or ongoing action. When creating PRs or issues, setting a label always comes after the creation event. Even if I set the label in the creation dialog, it's still two webhook events in the end. First "issue created" then "label set". Therefore omp-deck always triggers, and doesn't honor the label, because the event for it arrives afterwards. So a mechanism is needed where setting a label instructs the dispatcher to cancel. Even ongoing turns should be cancelled sometimes. This would cover both the case where I set the label during creation (the label event should arrive moments after the creation event) or when I forget and set later. I think for the second case, a small distinction is needed: automated actions, like "triage label applied", "review all PRs", etc. should be cancelled, while direct user interactions (reply to comment, `@mention`) probably shouldn't
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
lucas/omp-deck#275
No description provided.