I've encountered a recent problem, it applies to any new GitHub organisations I create.
I am admin for two fairly mature GitHub organisations. I can create repos within them, and everything "just works". (SmartGit, & CLI Git, OSX).
But, if I create a new organisation, I can't Push
to it, I get a 403 error:
$ git push
remote: Permission to [org]/[repo].git denied to [username].
fatal: unable to access 'https://github.com/[org]/[repo].git/':
The requested URL returned error: 403
$
Steps to reproduce:
I can make (& commit) changes via the GitHub.com web-page interface, but I can't push them from my local repo.
Note: From a different PC I can push to repos in existing organisations, but not the new ones. The other PC was still a Mac though, so it may be keychain related. Ok, I've tested it from a Windows VM, and it still fails. So, it does look like something at the GitHub end.
Any suggestions?
I installed GitKraken in a VM and in the GitHub authorisation process I had to indicate when organisations it could access. The new repo had a red Cross against it. I selected it, to allow GitKraken access to that organisation. GitKraken was then able to push to the new repo.
I then received an email telling me the GitHub authorisation had been added. It included a link to this page https://github.com/settings/connections/applications/
From that page I was able to view authorised OAuth apps. SmartGit (my normal Git client was listed). When I went into the page for that app, I saw it wasn't allowed access to my new organisation. I authorised access.
From that point on, I was able to push from either SmartGit or the command-line.