Resource not accessible by personal access token

[miteigidesu]

Select Topic Area

Question

Body

I'm trying to use this API endpoint:
/repos/{owner}/{repo}/merge-upstream

It needs the supplied PAT to have "Content" repository permission, as you can see from the documentary itself

My PAT has the correct permission it needed, as you can see:

But I got "Resource not accessible by personal access token" when trying to use the endpoint

Did I do something wrong? Or is this GitHub's bug?
Thanks in advanced :D

[RamezCh]

Hello @miteigidesu ,

Is the Personal Access token that you created from the type Fine-Grained? Did you select Contents permission and give it read + write?

[WaqasIshaque1]

1. Use Authorization: token YOUR_PAT instead of Bearer.
2. Make sure you're calling the API on your forked repo, not the original.
3. If using fine-grained PAT, ensure it has access to that repo and "Contents: Read and Write".
4. Use a classic PAT with repo scope if issue persists.

[RamezCh]

I'm curious about the difference between using Authorization: Token YOUR_PAT versus Authorization: Bearer YOUR_PAT.
As far as I can tell, both still work, but GitHub's documentation and most modern services prefer Bearer, which follows the standard OAuth2 format.
Also, I believe GH repo merge-upstream now requires a fine-grained PAT.

[miteigidesu]

Well I think my question answer most of them :D

[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! 💬