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. I'm afraid it's a while since I did this, so I forget the details. [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. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |