fix: handle Gitea 1.27's workflow_call event name in the trigger gate #21

Merged

steve merged 1 commits from fix/gitea-127-workflow-call into main

2026-07-16 03:00:41 +00:00

Author	SHA1	Message	Date
steveandClaude Fable 5	9d74cb9c81	fix: handle Gitea 1.27's workflow_call event name in the trigger gate Gadfly review (reusable) / review (pull_request) Successful in 28s Details Adversarial Review (Gadfly) / review (pull_request) Successful in 28s Details Build & push image / build-and-push (pull_request) Successful in 2m39s Details Gitea 1.27 (breaking change go-gitea#37478) runs a called (reusable) workflow with github.event_name = 'workflow_call' instead of propagating the caller's event. Every consumer stub forwards EVENT_NAME from github.event_name, so since the server upgrade every review arrived as an unhandled event and self-skipped in one second while reporting success — mort PRs #1445-#1447 all went unreviewed. Reclassify workflow_call from the forwarded payload: a non-empty COMMENT_BODY can only come from issue_comment (trigger-phrase + actor gates still apply); otherwise a PR number means a pull_request-shaped trigger. Neither → the existing unhandled-event skip. Pre-1.27 servers are unaffected. Co-Authored-By: Claude Fable 5 <[email protected]>	2026-07-15 23:00:09 -04:00

Author

SHA1

Message

Date

steveandClaude Fable 5

9d74cb9c81

fix: handle Gitea 1.27's workflow_call event name in the trigger gate

Gadfly review (reusable) / review (pull_request) Successful in 28s

Details

Adversarial Review (Gadfly) / review (pull_request) Successful in 28s

Details

Build & push image / build-and-push (pull_request) Successful in 2m39s

Details

Gitea 1.27 (breaking change go-gitea#37478) runs a called (reusable)
workflow with github.event_name = 'workflow_call' instead of propagating
the caller's event. Every consumer stub forwards EVENT_NAME from
github.event_name, so since the server upgrade every review arrived as an
unhandled event and self-skipped in one second while reporting success —
mort PRs #1445-#1447 all went unreviewed.

Reclassify workflow_call from the forwarded payload: a non-empty
COMMENT_BODY can only come from issue_comment (trigger-phrase + actor
gates still apply); otherwise a PR number means a pull_request-shaped
trigger. Neither → the existing unhandled-event skip. Pre-1.27 servers
are unaffected.

Co-Authored-By: Claude Fable 5 <[email protected]>

2026-07-15 23:00:09 -04:00