Triggers replace bindings, mappings, issue routing and playbooks #1978
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#1978
Reference in new issue
Block a user
One concept decides which events start which workflows: a trigger ("when this kind of event, matching this filter, happens: run that workflow with these inputs"). Bindings and mappings fold into it; issue routing and playbooks are removed. Forge issues reach workflows only as events on a source, through a trigger.
Done when: the API and dashboard expose triggers only; issue routing and playbooks are gone; a forge issue starts a workflow through a trigger like any other event.
Spec: section 4, R4, R8.
The maintainer keeps the capability behind bindings, mappings and playbooks: any sender pointed at a generated endpoint, its fields mapped onto a workflow's inputs. #2032 carries it into triggers (a CEL
whenand an input mapping, proposed by Archie as a draft). This issue's deletion of those paths waits for #2032.