docs(adr): synchronous workflow_call for event-driven agent dispatch - #1245
Conversation
Site previewPreview: https://17f5fae4-site.fullsend-ai.workers.dev Commit: |
ReviewFindingsNo findings. Previous runReviewFindingsNo findings. Previous run (2)ReviewFindingsNo findings. Previous run (3)ReviewFindingsNo findings. |
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. |
Then I'm understanding the feature wrong. However not sure if it is even relevant. Nevermind then |
ae37296 to
6fefc29
Compare
Replace dispatch.yml gh workflow run fan-out with workflow_call for UI traceability, and drop ADR 26 dynamic agent discovery without adding a compile-time sync substitute. Discovery may be revisited after ADR 38. Signed-off-by: Barak Korren <bkorren@redhat.com>
6fefc29 to
5fa8757
Compare
Summary
dispatch.yml→ stageworkflow_dispatch/gh workflow runwith synchronousworkflow_callso Actions runs stay linked for PR/issue debugging.Test plan
pre-commit run --files docs/ADRs/0041-synchronous-workflow-call-event-dispatch.mdMade with Cursor