Unable to push to repo where I have write access

In my previous thread, i ran into a problem: https://github.community/t5/How-to-use-Git-and-GitHub/Unable-to-fork-Erroneously-saying-i-already-have-a-fork-of-it/m-p/31301#M8568

I’ve decided to solve this problem by getting deeper access with a project I contribute to, so that I no longer need to maintain my own fork of their repo and can delete it.

The project leader has added me as a Collaborator with write access, but I am still unable to push my work to new branches on that repo. When i try to push anything to a branch there, i get this error

C:\Projects\DeadSpace13\baystation12> git.exe -c "credential.helper=C:/Program\ Files/Smartgit/lib/credentials.cmd" push --porcelain --progress --recurse-submodules=check upstream refs/heads/AccessRework2:refs/heads/AccessRework2
remote: Permission to DS-13-Dev-Team/Dead-Space-13.git denied to NanakoAC.
unable to access 'https://github.com/DS-13-Dev-Team/Dead-Space-13/': The requested URL returned error: 403

The obvious thought would be that write access isn’t setup properly, but I believe it is. Because here’s the UI of a pull request I have open to that repo:

Note things like the little cog buttons in the sidebar, and the button to merge the request. I didn’t have those earlier today before we added my new status.  I tested the buttons, i can indeed add labels to things. In my experience that can only be done with write access. So we don’t understand what’s going on here, the owner of the repo knows less than I do, we’ve looked up several tutorials and help pages, but failed to make it work

As for how i’m actually trying to push, here’s how:

Using smartgit, Push To, selecting upstream, i’m fairly sure the url there is correct.

I plan to change my origin to that url once we get this working, it currently points at my own fork of this repo which, as explained, i want to delete.

Can anyone speculate on what might be wrong? Any settings we could try to change? Anything i’m doing incorrectly?

1 Like

Hi @nanakoac!

My first guess would be that your local Git setup is not authenticating you correctly to GitHub. Are you able to use that setup to push to your own private repository?