![]() That may or may not be helpful, but I hope you can find a solution. Is it just a private repo you're wanting to access, or a private organization repo? If the latter, from that first link I think an organization owner has to grant access for the app (so I guess even if you have access as a GitHub user, you don't automatically get access when using the app). However, whenever I tried to push or pull or do anything with the remote branch from my Sourcetree, I got the following error: remote: Repository not found. ![]() You may well have already looked here, but I found this on an initial google: However, I'd be surprised if it's not possible to access private repos at all this way. So it could well be that the solution for that is different. So the commonality of my problem with the original question here was "organization repos not appearing" rather than the private/public dimension of the question. But certainly the repos I was concerned with were public ones, just that they belonged to an organization. First I went to my Authorized OAuth App Settings at /settings/applications and removed the Sourcetree one: Then I opened my accounts settings in. If you have already cloned the repo, skip to the Working with branches section. ![]() Cloning the repo will grab the latest files from the Github repository and save it to your computer. I'm afraid it's a while since I did this, so I forget the details. Clone the repo You only have to do this step once. [This Medium article described the same problem and solution, except that they suggest deleting and re-creating the OAuth token, whereas I was able to just edit the settings on mine: not sure if is the same/similar problem to above, but I came across this question when searching for a solution, so thought it good to add my solution here after I worked out what my issue was.) To fix, go to your GitHub settings -> Applications -> Authorized OAuth Apps -> Sourcetree ('SourcetreeForWindows' in my case): you can see the list of permissions granted, and underneath that Organization access, and the option to turn it on. cause This SSH key was a Sourcetree, created and registered, restricted by OAuth App access restrictions, and restricted to access only personal repositories (repositories under NOT Organization). Maybe the credentials that SourceTree uses are invalid You could try to reset them or switch to the system git client. I discovered it was an issue with the default permissions in the OAuth settings by default, it doesn't give organization access. I tried starring the relevant one, but that didn't make a difference. After this the remote repositories became visible. I had a similar problem after adding my GitHub account to SourceTree, repos belonging to my organization weren't appearing in the 'Remote repositories' list. I selected OAuth for authentication and clicked Refresh OAuth Token.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |