Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 3 additions & 17 deletions e2e/behaviour/features/dispatch/dispatch.feature
Original file line number Diff line number Diff line change
Expand Up @@ -25,26 +25,12 @@ Feature: Harness CEL dispatch
| Payload has issue number | assert_json | .fullsend/dispatch/event-payload.json,issue.number |
| Prove execution | write_fixture| output/dispatch-ok.json, fixtures/dispatch/ok.json |
And an issue
When the issue is labeled "wrong-label"
Then the harness "issue-ping" agent did not run
When the issue is labeled "ready-for-ping"
Then the harness "issue-ping" workflow completes successfully
And the agent will succeed to Prove execution

Scenario: Wrong label does not trigger issue 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"
"""
And an issue
When the issue is labeled "wrong-label"
Then the harness "issue-ping" agent did not run
And the harness "issue-ping" was dispatched exactly 1 time

Scenario: PR does not trigger issue-only harness
Given a custom harness "issue-ping" with:
Comment thread
ifireball marked this conversation as resolved.
Resolved
Expand Down
Loading