Skip to content

test(#5494): fold fork-PR issue-harness negative into fork-label positive #5501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ifireball merged 1 commit into from
Jul 23, 2026
Merged

test(#5494): fold fork-PR issue-harness negative into fork-label positive #5501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
29 changes: 13 additions & 16 deletions e2e/behaviour/features/dispatch/fork-dispatch.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand All @@ -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:
Expand All @@ -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
Loading