Replies: 4 comments
|
Your trigger config is fine. Read-only diagnostics, all with # 1. Repo-level Actions state: expect "enabled": true
gh api repos/OWNER/REPO/actions/permissions
# 2. Workflows GitHub has registered, and whether one is disabled
gh api repos/OWNER/REPO/actions/workflows --jq '.workflows[] | {name, path, state}'
# 3. Runs the UI might be hiding (filtered by branch and event)
gh api "repos/OWNER/REPO/actions/runs?branch=setup/ci-bootstrap" --jq '.total_count'
gh api "repos/OWNER/REPO/actions/runs?event=pull_request" --jq '.total_count'
# 4. The real discriminator: did Actions create a check suite for the pushed commit?
gh api repos/OWNER/REPO/commits/HEAD_SHA/check-suites \
--jq '.check_suites[] | select(.app.slug=="github-actions") | {status, conclusion, latest_check_runs_count}'How to read 4: on a healthy repo every pushed commit gets a Control test that settles it in two minutes: create a throwaway public repo on the same account, commit a one-job Billing check, if you want to rule it out explicitly: Nothing in the setup PR needs to change before merging. Merging to the default branch will not create a run on its own either if the account is blocked. |
|
Hi @community! If a new workflow produces no runs on a private repo:
|
|
Your You can inspect the repository's Actions permissions with: gh api repos/OWNER/REPO/actions/permissionsThen check the registered workflows: gh api repos/OWNER/REPO/actions/workflows \
--jq '.workflows[] | {name, path, state}'Replace Also check the workflow run history and repository Actions settings. If the workflow is registered and enabled but no runs are created, inspect the repository's event and permission settings before changing the YAML. If this solves your issue, please mark this reply as the answer. It will help others facing the same problem find the solution more easily! |
|
One caveat on the workflow inventory check: For a read-only check, use the exact SHA from the branch push and the PR head with |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
I'm troubleshooting a new private repository on a personal GitHub Free account. A workflow committed through GitHub's web editor exists at
.github/workflows/ci.ymlon branchsetup/ci-bootstrap, but the Actions page has no runs and the pull request shows Checks (0). There is no workflow error or failed run to inspect.The relevant trigger configuration is:
The workflow defines a job on a GitHub-hosted Ubuntu runner. It uses read-only Contents permission, no secrets, and the official checkout action pinned to a full commit hash with persisted credentials disabled. The default branch currently contains only a README; the workflow is proposed through the setup PR. A separate read-only Git fetch verified the file and its triggers at the PR head.
What I have checked:
I expected the push trigger to run on the named setup branch, and the PR trigger to create a check. Which read-only diagnostics can distinguish a workflow-discovery problem from an account-side Actions restriction? Is there another bootstrap requirement I should check before merging any setup change?
Thanks for any pointers. I can share non-sensitive diagnostics, but the repository will remain private.
All reactions