GitHub Actions never creates workflow runs in my public repository

[NicolaGarciaE]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

Hello,

GitHub Actions has never created a workflow run in my public repository https://github.com/NicolaGarciaE/threat-intel-pipeline, and I would like to know whether Actions is disabled, restricted or stuck for this repository or for my account (NicolaGarciaE).

Pull request NicolaGarciaE/threat-intel-pipeline#5 (branch session-4-ci, head commit b47c3bc5bd751ae6a1830fb9fbfd79afd48fcb37, base main) adds .github/workflows/ci.yml, which runs on pull_request with branches: [main]. None of these pull_request events created a workflow run, a check suite or a check from GitHub Actions (all times UTC, 2026-11-04):

• 10:24:43: iOS bug report: strange backstack behavior when navigating to a file #4 opened, during the incident "Incident with Pull Requests, Git Operations and Issues" (09:49 to 11:50);
• 12:02:51: iOS bug report: strange backstack behavior when navigating to a file #4 reopened, after the incident was resolved;
• 12:31:16: Feature request: support jumping to lines in files #5 opened from the same branch, after closing iOS bug report: strange backstack behavior when navigating to a file #4;
• 12:58:32: Feature request: support jumping to lines in files #5 reopened.

What I checked:

• GET /repos/NicolaGarciaE/threat-intel-pipeline/actions/runs and GET /repos/NicolaGarciaE/threat-intel-pipeline/actions/workflows both return total_count 0.
• The only check suite on the head commit belongs to another GitHub App ("claude"); there is none from GitHub Actions on the head commit or on the test merge commits.
• In the head commit and in the latest test merge commit, the git tree contains exactly .github/workflows/ci.yml and .github/workflows/daily.yml; ci.yml has no BOM and LF line endings.
• The pull request has no merge conflicts, and no commit contains [skip ci]-type strings or a skip-checks trailer.
• ci.yml passes actionlint 1.7.12 with no findings.
• Actions permissions: enabled true, allowed_actions all. The fork pull request approval policy is all_external_contributors; I am the owner of the repository and the author of the pull request. "Require actions to be pinned to a full-length commit SHA" was disabled for the last reopen (12:58) and enabled before and after it: no run either way.
• The Actions tab shows "Get started with GitHub Actions" and no message saying that Actions is disabled.
• githubstatus.com shows every component as operational and no open incident.
• No other repository of my account has workflows, so Actions has never run on this account before.

Could you check whether GitHub Actions is blocked for this repository or for my account, and tell me what I need to do?

Thank you,
Nicola García

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[thiagocaggiano]

Two facts from the API that narrow this down:

• main has no .github directory at all; ci.yml and daily.yml exist only on session-4-ci. That is fine for pull_request (Actions reads the workflow from the PR merge commit), and it is also why GET /actions/workflows returns 0: that endpoint lists the default branch.
• The head commit b47c3bc has exactly one check suite, from the claude app, stuck in queued. No Actions check suite was ever created for any of the four events, including the two after the incident ended.

When pull_request events never even create a check suite, the workflow file is rarely the problem. Actions can be disabled at the account level by GitHub's abuse prevention while the repository settings API still reports enabled: true. There is a thread with the same symptom from Oct 31: #211750 "GitHub Actions disabled on my account: owner invocation blocked".

Quick way to tell the two cases apart:

1. Push an empty commit to session-4-ci (git commit --allow-empty -m "retrigger" && git push). This emits a fresh synchronize event outside the incident window. If a run appears, the earlier events were lost during the incident and you are done.
2. If nothing appears, push a one-job workflow_dispatch workflow to main and run gh workflow run . If gh run list stays empty, Actions is blocked for the account and only Support can lift it; attach the API evidence above to the ticket.