docs(adr): synchronous workflow_call for event-driven agent dispatch#1245
docs(adr): synchronous workflow_call for event-driven agent dispatch#1245ifireball wants to merge 1 commit into
Conversation
Record ADR 0039 to replace dispatch.yml gh workflow run fan-out with workflow_call for UI traceability, and compile-time dispatch sync for org custom agents in .fullsend. Co-authored-by: Cursor <[email protected]>
Site previewPreview: https://8a28cfed-site.fullsend-ai.workers.dev Commit: |
ReviewFindingsNo findings. Previous runReviewFindingsNo findings. |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
fullsend-ai-review
Bot
added
the
ready-for-merge
fullsend-ai-review
Bot
added
ready-for-merge
There was a problem hiding this comment.
I agree.
Did we take into account the billing for GH actions? There limits are very large in terms of minutes, but I don't know if this would be doubling minute usages for orgs using fullsend.
As a side note it is always funny how a lot of ADR frame options are very one sided.
Not quite sure why are you claiming this particular ADR would contribute towards more usage minutes, it could end up being cheaper if e.g. workflow_call is cheaper then workflow_dispatch. |
Yes, I'm being explicit about that, trying to find a middle ground where we would add build time tooling and CI to do "agent discovery" instead a fully dynamic discovery which requires async dispatch. |
3 participants
Summary
dispatch.yml→ stageworkflow_dispatch/gh workflow runwith synchronousworkflow_callso Actions runs stay linked for PR/issue debugging.# fullsend-stage:metadata, a scaffoldedsync-dispatchscript, skills, and CI in.fullsend(follow-on implementation).Test plan
make linton ADR 0039Made with Cursor