Error 403 When trying to clone a private shared repo

[apmsabee]

Select Topic Area

Question

Body

Me and a project partner are trying to use GitHub to collaborate on our code for a class. He set up the repository, made it private, and invited me as a collaborator. Every time I try to use git clone to download the repo to my machine, I get error 403, and the message "remote: write access to repository not granted." How do I fix this?

[airtower-luna]

Could you share the exact and full commands you used and output you got? You can censor the repository name, but the details matter.

The error message you already shared seems odd at least, because cloning shouldn't require write access (it only copies data from remote to your machine).

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

[juangroening]

The same thing happens to me. I can clone it with the github desktop but not with the console.

[bucklevision]

Me too.
git clone https://[email protected]/username/repo.git

returns:
git clone https://[email protected]/username/repo.git
remote: Write access to repository not granted.
fatal: unable to access 'repo url': The requested URL returned error: 403

I'm guessing I've got a permissions error on my token setup but I've no idea which permission needs to be write-enabled to just clone the repo.

[rohan-reddy-p]

Did you find a solution?

[sujalcharati]

Did you find a solution?

Did you find a solution?

[Natalia-Lovich]

I had the same issue and fixed it by creating a new token (Personal Access Tokens - classic) and checking everything in the list. I suppose not everything is required.

[TomasHubelbauer]

Thanks, this helped me. For some reason I assumed that checking no scopes meant all scopes would apply in the case of the classic PAT. Seems useless that the UI allows you to create a PAT with no scopes.