-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
area:ciCI/CD, GitHub Actions, workflowsCI/CD, GitHub Actions, workflowsarea:workflowDeveloper workflow, commands, rules, skillsDeveloper workflow, commands, rules, skillsbugSomething isn't workingSomething isn't workingeffort:smallLess than 1 hourLess than 1 hourpriority:mediumImportant but not urgentImportant but not urgentsemver:patchBug fix, backward-compatibleBug fix, backward-compatible
Description
Description
The smoke-test repository_dispatch deploy flow intermittently fails in the step Commit and push deploy changes via signed commit-action with a Git refs Not Found error, even when the target branch exists and a retry of the same dispatch later succeeds.
Steps to Reproduce
- Trigger smoke-test dispatch with tag
0.3.1-rc3:gh api repos/vig-os/devcontainer-smoke-test/dispatches -f event_type=smoke-test-trigger -f 'client_payload[tag]=0.3.1-rc3' -f 'client_payload[release_kind]=candidate'
- Observe one run failing in deploy step:
- Trigger the same dispatch again with the same payload.
- Observe deploy step succeeding in a later run:
Expected Behavior
The deploy commit step is deterministic and succeeds consistently for identical dispatch payloads, or performs bounded retry for transient API/token failures.
Actual Behavior
Intermittent failure in vig-os/commit-action:
Not Found - https://docs.github.com/rest/git/refs#get-a-reference
This occurs after branch preparation and after logging Using TARGET_BRANCH: chore/deploy-0.3.1-rc3.
Environment
- OS: GitHub-hosted runner
ubuntu-22.04 - Container Runtime: N/A (workflow-side GitHub API operation)
- Image Version/Tag: smoke-test dispatch tag
0.3.1-rc3 - Architecture: x86_64 (GitHub-hosted runner)
Additional Context
- Relevant workflow template:
assets/smoke-test/.github/workflows/repository-dispatch.yml create-github-app-tokenis pinned to v3 SHA in the current template.- Proposed mitigation: add one bounded retry around commit-action with fresh commit-app token mint before retry.
- TDD compliance (see
.cursor/rules/tdd.mdc)
Possible Solution
Implement a targeted retry block only for Commit and push deploy changes via signed commit-action:
- attempt once with current token,
- on failure, re-mint commit app token,
- retry once after short backoff,
- fail hard if second attempt fails.
Changelog Category
No changelog needed
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:ciCI/CD, GitHub Actions, workflowsCI/CD, GitHub Actions, workflowsarea:workflowDeveloper workflow, commands, rules, skillsDeveloper workflow, commands, rules, skillsbugSomething isn't workingSomething isn't workingeffort:smallLess than 1 hourLess than 1 hourpriority:mediumImportant but not urgentImportant but not urgentsemver:patchBug fix, backward-compatibleBug fix, backward-compatible