fix(autopilot): merge via AGENT_TOKEN so it triggers deploy #52

2026-07-04T22:32:13+02:00

ffaerber commented

2026-07-04 22:32:13 +02:00

@qa's autopilot merge used the built-in Actions token, and Gitea doesnt fire workflows for pushes made by that token — so the merge landed on main but deploy.yml never ran (merged-but-not-deployed, seen on PR #131 / issue #130). Merge with AGENT_TOKEN (a PAT) so the push triggers the deploy.

ffaerber added 1 commit 2026-07-04 22:32:14 +02:00

fix(autopilot): merge with AGENT_TOKEN so the merge triggers the deploy cf1e7178b5

@qa's autopilot merge used the built-in Actions token (TOKEN_QA unset -> fell back to GITEA_TOKEN).
Gitea does not fire new workflow runs for pushes made by the built-in Actions token, so the merge
landed on main but deploy.yml never ran — the change was merged-but-not-deployed. Merge with
AGENT_TOKEN (a PAT, already used for delegation and proven to trigger runs) so the push to main
triggers the deploy.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

ffaerber merged commit 4cbbc9b2d7 into main

2026-07-05 08:05:43 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gitea/agents#52