fix: chain coder build via explicit workflow-dispatch #23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/workflow-dispatch-chain"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #22
Problem
workflow_runis not reliably triggering in Forgejo — the coder build was silently not firing after the base build succeeded.Fix
build.yamlAdded a final step using
git.michaelsagger.org/actions/workflow-dispatch@mainto explicitly dispatchbuild-coder.ymlafter a successful base build. This is the approach Brad suggested in the issue.build-coder.ymlSimplified trigger to
workflow_dispatchonly — removes the unreliableworkflow_runtrigger and the associatedif:condition in the job. The explicit dispatch frombuild.yamlguarantees ordering and only fires on success.Flow after this fix
No more manual triggering required.
see comment
@ -40,2 +40,4 @@docker tag ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:rbw openclaw-sandbox:rbwdocker tag ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:rbw openclaw-sandbox:latest- name: Trigger coder buildcan't we make this depend on the success of the preivous build step?
Good call —
needs:is cleaner and avoids the external action entirely.Updated the PR: consolidated both workflows into a single
build.yamlwith two jobs:build-coder.ymlis gone. Theneeds:dependency guarantees ordering and only fires on success — native to Forgejo, no third-party action required.no sorry i prefer two workflows. just revert to the previous that's good enough
Reverted the consolidation — two workflows are back.
build.yamldispatchesbuild-coder.ymlvia workflow-dispatch when the base build succeeds. Same flow as before theneeds:attempt.Ready for re-review.