diff --git a/e2e/behaviour/features/dispatch/fork-dispatch.feature b/e2e/behaviour/features/dispatch/fork-dispatch.feature index f6f11e0b77..45b8072b48 100644 --- a/e2e/behaviour/features/dispatch/fork-dispatch.feature +++ b/e2e/behaviour/features/dispatch/fork-dispatch.feature @@ -17,6 +17,18 @@ Feature: Fork PR dispatch && event.transition.kind == "label_changed" && event.transition.label.name == "ready-for-fork-ping" """ + And a custom harness "fork-issue-ping" with: + """ + agent: agents/triage.md + role: triage + slug: fullsend-ai-fork-issue-ping + model: opus + image: ghcr.io/fullsend-ai/fullsend-sandbox:latest + trigger: | + event.entity.kind == "work_item" + && event.transition.kind == "label_changed" + && event.transition.label.name == "ready-for-fork-ping" + """ And a dummy agent that would: | description | op | args | | Fork PR payload | assert_json | .fullsend/dispatch/event-payload.json,pull_request.head.repo.fork | @@ -26,6 +38,7 @@ Feature: Fork PR dispatch Then the harness "fork-pr-ping" workflow completes successfully And the agent will succeed to Prove fork execution And the harness "fork-pr-ping" was dispatched exactly 1 time + And the harness "fork-issue-ping" agent did not run Scenario: Fork PR sync + label dispatches harness Given a custom harness "fork-pr-sync" with: @@ -50,19 +63,3 @@ Feature: Fork PR dispatch Then the harness "fork-pr-sync" workflow completes successfully And the agent will succeed to Prove sync execution And the harness "fork-pr-sync" was dispatched exactly 1 time - - Scenario: Fork PR does not trigger issue-only harness - Given a custom harness "issue-ping" with: - """ - agent: agents/triage.md - role: triage - slug: fullsend-ai-issue-ping - model: opus - image: ghcr.io/fullsend-ai/fullsend-sandbox:latest - trigger: | - event.entity.kind == "work_item" - && event.transition.kind == "label_changed" - && event.transition.label.name == "ready-for-ping" - """ - When a fork pull request is opened - Then the harness "issue-ping" agent did not run