fix: forward event_name from the canonical caller #1

Merged

ellen merged 1 commit from fix/caller-event-name into main

2026-07-23 11:39:53 +00:00

cloudcli commented

2026-07-23 11:37:14 +00:00

Member

Why

The canonical caller lives here in the template so every repo created from it already ships a working .forgejo/workflows/agent.yaml — one source of truth, no per-repo syncing.

This updates it to forward the trigger: with: { event_name: ${{ github.event_name }} }. Forgejo sets github.event_name to workflow_call inside a called reusable workflow (unlike GitHub), so the dispatcher can't otherwise tell a schedule tick from a label event. Found in the first end-to-end test (see valssi/docs → plans/agent-orchestration-test-findings.md).

Depends on

valssi-public/agent-workflows PR #14 — it adds the matching workflow_call input event_name (plus the other Forgejo event-semantics fixes). Passing with: event_name before that input exists would error, so merge PR #14 first, then this.

Note

The companion PR #14 originally carried a caller-agent.yaml copy; that has been removed there so this template file is the single source of truth for the caller.

🤖 Generated with Claude Code

## Why The canonical caller lives here in the template so every repo created from it already ships a working `.forgejo/workflows/agent.yaml` — one source of truth, no per-repo syncing. This updates it to forward the trigger: `with: { event_name: ${{ github.event_name }} }`. Forgejo sets `github.event_name` to `workflow_call` inside a called reusable workflow (unlike GitHub), so the dispatcher can't otherwise tell a schedule tick from a label event. Found in the first end-to-end test (see `valssi/docs` → `plans/agent-orchestration-test-findings.md`). ## Depends on **`valssi-public/agent-workflows` PR #14** — it adds the matching `workflow_call` input `event_name` (plus the other Forgejo event-semantics fixes). Passing `with: event_name` before that input exists would error, so **merge PR #14 first**, then this. ## Note The companion PR #14 originally carried a `caller-agent.yaml` copy; that has been removed there so this template file is the single source of truth for the caller. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

cloudcli added 1 commit

2026-07-23 11:37:14 +00:00

fix: forward event_name from the canonical caller

agent / tick (pull_request) Has been skipped

Details

agent / resolve (pull_request) Successful in 1s

Details

agent / dev (pull_request) Has been skipped

Details

agent / implement (pull_request) Successful in 0s

Details

agent / dev-bounce (pull_request) Successful in 0s

Details

agent / plan (pull_request) Has been skipped

Details

agent / coordinate (pull_request) Has been skipped

Details

agent / reflect (pull_request) Successful in 0s

Details

agent / test (pull_request) Successful in 0s

Details

agent / dispatch (pull_request) Successful in 0s

Details

0d7dae02f5

Forgejo sets github.event_name to 'workflow_call' inside a called reusable
workflow, so the dispatcher can't distinguish a schedule tick from a label
event. Forward the real trigger via with: event_name.

Requires valssi-public/agent-workflows PR #14 (adds the matching workflow_call
input + the Forgejo event-semantics fixes) to be merged first.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>