Problem
After PR #71 was squash-merged to master, GitHub Actions created a failed run for .github/workflows/sync-issues.yml on the push event:
gh run view --log-failed returns failed to get run log: log not found, so there is no job-level evidence to inspect. The workflow file currently declares issues, schedule, and workflow_dispatch triggers, not push, which makes this failure ambiguous.
Impact
The main CI workflow for the same merge commit is green, but the repository still shows an extra failed workflow run after merge. That makes remote health look worse than the actual code/test state.
Acceptance
- Determine why
sync-issues.yml records a failed push run with no jobs/logs.
- Either fix the workflow trigger/config or document the GitHub Actions behavior if it is external.
- Confirm future issue sync events and master pushes do not leave unexplained failed runs.
Problem
After PR #71 was squash-merged to
master, GitHub Actions created a failed run for.github/workflows/sync-issues.ymlon the push event:push3038baeb1f7eb27af4b681c75a5e7cbc8a13d82cfailure[]gh run view --log-failedreturnsfailed to get run log: log not found, so there is no job-level evidence to inspect. The workflow file currently declaresissues,schedule, andworkflow_dispatchtriggers, notpush, which makes this failure ambiguous.Impact
The main CI workflow for the same merge commit is green, but the repository still shows an extra failed workflow run after merge. That makes remote health look worse than the actual code/test state.
Acceptance
sync-issues.ymlrecords a failed push run with no jobs/logs.