Typist #3498

Activity

1. github-actions commented on Nov 8, 2025

   

   github-actionsBot

   on Nov 8, 2025 – with GitHub Actions

   Contributor

   More actions

   Agentic Q triggered by this issue.
2. github-actions commented on Nov 8, 2025

   

   github-actionsBot

   on Nov 8, 2025 – with GitHub Actions

   Contributor

   More actions

   Investigation Results for Run #19197605256

   The workflow run https://github.com/githubnext/gh-aw/actions/runs/19197605256 shows 0 jobs and a "failure" conclusion, but this is actually expected behavior and not a bug.

   Root Cause

   The typist.lock.yml workflow is configured to run on:

   • schedule: cron: "0 11 * * 1-5" (weekdays at 11 AM UTC)
   • workflow_dispatch (manual trigger)

   However, run #19197605256 was triggered by a push event on the copilot/fix-super-linter-config branch:

   Event: push
   Branch: copilot/fix-super-linter-config
   Commit: c4704418d9f87eb4e79ae4218ea536a302c87701
   Message: "Add Super Linter workflow for code quality analysis and reporting"
   

   Since push is not in the workflow's trigger list, GitHub Actions correctly:

   1. Created a workflow run record (for tracking)
   2. Skipped all jobs (because the trigger didn't match)
   3. Marked it as "failed" (GitHub's way of indicating "did not run")

   Why This Happens

   When a .lock.yml file exists in .github/workflows/, GitHub Actions creates run records for all events, even if the workflow isn't configured to run on that event. The "0 jobs, failure" outcome indicates the workflow was skipped due to trigger mismatch.

   Verification

   I verified the workflow compiles correctly:

   $ gh aw compile typist --no-emit
   ✓ .github/workflows/typist.md
   ✓ Compiled 1 workflow(s): 0 error(s), 0 warning(s)

   The jobs section exists in the compiled .lock.yml file and is properly configured.

   Conclusion

   This is not a workflow failure - it's GitHub Actions' expected behavior when a workflow file exists but the trigger doesn't match the event. The typist workflow will run successfully when triggered via:

   • Manual workflow_dispatch
   • Scheduled cron trigger (weekdays at 11 AM UTC)

   No action needed. ✅

   AI generated by Q for #3498
3. pelikhan

   closed this as completedon Nov 11, 2025