gh cli api returns 404 but I think auth is OK; what am I doing wrong?

[garyo]

Select Topic Area

Question

Body

I have the latest gh CLI app. I set a GH_TOKEN. It seems to be working, because this works:

gh api --method GET -H "Accept: application/vnd.github.v3+json" "orgs/MyOrg/repos"

...it returns a few repos.

But this call returns a 404:

gh api --method GET -H "Accept: application/vnd.github.v3+json" "repos/MyOrg/MyRepo/actions/runners"

even though my (classic) token has full repo scope as well as read:org and manage_runners:org.
What I'm really trying to do is create a self-hosted runner, and this doesn't work either:

 gh api --method POST -H "Accept: application/vnd.github.v3+json" "/repos/MyOrg/MyRepo/actions/runners/registration-token"

that also returns a 404. Any hints?

[lbirkert]

Select Topic Area

Question

Body

I have the latest gh CLI app. I set a GH_TOKEN. It seems to be working, because this works:

gh api --method GET -H "Accept: application/vnd.github.v3+json" "orgs/MyOrg/repos"

...it returns a few repos.

But this call returns a 404:

gh api --method GET -H "Accept: application/vnd.github.v3+json" "repos/MyOrg/MyRepo/actions/runners"

even though my (classic) token has full repo scope as well as read:org and manage_runners:org. What I'm really trying to do is create a self-hosted runner, and this doesn't work either:

 gh api --method POST -H "Accept: application/vnd.github.v3+json" "/repos/MyOrg/MyRepo/actions/runners/registration-token"

that also returns a 404. Any hints?

G'day sir,

The 404 hints to the repository not being found/the token not having permissions for accessing this repo (Is it private?). Make sure you checked the spelling and make sure the repository is included in this list: gh api --method GET -H "Accept: application/vnd.github.v3+json" "orgs/MyOrg/repos"

Take care

[ghostinhershell]

Hey @garyo,

Just tagging you here just in case you haven't seen @KekOnTheWorld's response here. Does this answer your question?

[jsoref]

So, I recently was convinced (by gh) to run: gh auth refresh -h github.com -s admin:org (and then grant the permission).

Having done that, gh api "repos/check-spelling/check-spelling/actions/runners" yields:

{
  "total_count": 0,
  "runners": []
}

and that seems reasonable (I'm not using self-hosted runners for that repository)...

[jsoref]

I had no trouble using:

gh auth refresh -h github.com -s admin:org
gh api --method POST -H "Accept: application/vnd.github.v3+json" "/repos/$ORG/$REPO/actions/runners/registration-token"

The version of gh I'm using nudged me to use the gh auth refresh command...

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬