Replies: 2 comments
|
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. |
|
Yes, this issue typically happens when GitHub's internal webhook subscriber for the Actions service becomes desynchronized or unhooked from the repository's git ref event pipeline, especially on newly created repositories or repositories where branch names were toggled. Since Step 1: Force a Webhook Resync by Toggling ActionsToggling the Actions state forces GitHub's internal database to teardown and re-bind all system event hooks:
Step 2: Toggle the Default Branch RefIf the repository had its default branch renamed (or created with
Step 3: Trigger via a Pull Request to Re-register Check SuitesSometimes the
Step 4: GitHub Support InterventionIf Steps 1–3 do not kick the listener, it indicates an orphaned entry in GitHub's internal routing table (specifically the internal hook ID that dispatches repository
Support can run a backend repair script that takes less than a minute. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
In one of my private repositories (personal account, Free plan), pushing to
mainhas nevercreated a workflow run, for any workflow, since the repository was created. Running the same
workflow manually with
workflow_dispatchworks every time, so Actions is enabled and theworkflow file is valid.
What I see
GET /repos/{owner}/{repo}/actions/runs?event=pushreturnstotal_count: 0; every run in therepository was started with
workflow_dispatch.main, no Actions check suite and no workflow runappeared, even after waiting several minutes. The Vercel GitHub App received the same push
(its check suite and commit status exist on that commit), so the push itself reaches GitHub.
PushEventin the repository Events API.v*) did not start the tag-triggered release workflow either.What I have ruled out
enabled: true,allowed_actions: all; both workflows areactive.on: push: branches: [main](pluspull_requestandworkflow_dispatch). There isno
paths/paths-ignore/branches-ignore, and no job-levelifthat could skip a push.concurrencyonly cancels in-progress runs.main, identical locally and on GitHub; valid YAML (manual runssucceed).
[skip ci],[ci skip],[no ci],[skip actions],[actions skip]orskip-checks:in the commit messages.repo,workflow),not
GITHUB_TOKENand not a GitHub App installation token.main.read(should not affect triggering).Question
Has anyone seen push events not being dispatched to Actions for one repository while
workflow_dispatchworks? Is there a repository- or account-level state (a stuck webhooksubscription for the Actions app, for example) that can cause this, and a way to reset it
without recreating the repository? I have also opened a support ticket.
Current workaround: a local
pre-pushhook that waits for the push to land and then runsgh workflow run CI --ref main.All reactions