push/pull_request workflow runs not triggering for one repo (schedule + workflow_dispatch still fire)

[jeremylongshore]

Since 2026-06-30 ~06:26 UTC, my public repo jeremylongshore/intent-eval-lab has stopped creating Actions runs for push and pull_request events. Scheduled and manual runs still work, so it appears to be a stuck per-repo event subscription for push/PR specifically.

Evidence

• Last pull_request-triggered run: 06:26 UTC. None since, despite 6+ pushes / force-pushes (new commit SHAs), closing & reopening the PR, and creating a brand-new branch + PR.
• schedule (cron) and workflow_dispatch runs DO still fire in this same repo — e.g. scheduled jobs completed at 10:17, 10:37, and 11:07 UTC the same day, and a workflow_dispatch deploy fired normally.
• Config is healthy: Actions is enabled, all workflows are active, allowed_actions = all, the workflows have no path filters (on: pull_request / push: branches:[main]), and there are no queued/stuck runs.
• I toggled Actions off → on via both the REST API and the Settings UI (waited for propagation, then re-triggered) — no effect.
• Isolation check: a controlled probe (an empty-commit PR) in a sibling public repo (jeremylongshore/intent-rollout-gate) fired all of its checks instantly. So this is not account-wide and not a global incident — it's isolated to intent-eval-lab.

Ask

This looks like a stuck/broken per-repo event delivery for push + pull_request to Actions. Could someone re-register / repair event delivery for jeremylongshore/intent-eval-lab? Happy to provide specific run IDs, commit SHAs, and timestamps.

Environment

• Repo: jeremylongshore/intent-eval-lab (public)

• Plan: GitHub Free

• Onset: 2026-06-30 ~06:26 UTC

• Unaffected in same repo: schedule, workflow_dispatch

• Affected: push, pull_request

• Jeremy Longshore
  intentsolutions.io

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.