push access denied after "personal access token (classic)" regenerated

[Papa-26]

Select Topic Area

General

Body

Roughly every 2 months I am asked to regenerate my PAT(classic), which I do. Since the most recent one, I am unable to push recent project changes on one of my projects. I have tried every one of of my past PATs, and all end in 'access denied'.
What should I do?

Username for 'https://github.com': xxxxx
Password for 'https://[email protected]':
remote: Permission to Papa-26/yyyyy.git denied to xxxxxx.
fatal: unable to access 'https://github.com/xxxx/yyyyy/': The requested URL returned error: 403

[thevindu-w]

May be you can try creating a new token and use that. Make sure to add the necessary permissions to the PAT (in your case, write access to repo)

[Papa-26]

I am a bit confused about the whole PAT business. I have two kind of projects: Organization projects (where I happen to be responsible for the organization), and private projects, that have nothing to do with the organization. Up to now I have used the same PAT for both projects. My problem is with a private project. How do I untangle the access privileges?

[thevindu-w]

You can view/change the access privileges for tokens at https://github.com/settings/tokens. It should have repo privileges. For example, it can look like,

[Papa-26]

Thank you thevindu-w for your help. It worked perfectly, and I am able to function again. It was very generous of you, to offer your time to fix my problem.
Papaworx-26