-
Notifications
You must be signed in to change notification settings - Fork 3
Galaxy Detects No Roles in GitHub #217
Comments
|
There is an account on Galaxy for username ChrisShort, however it does not appear to be associated with a GitHub username. Let's start by fixing that. First, if you have previously accessed Galaxy via the browser you're using, clear the browser's history, removing cookies. Now authenticate with Galaxy using your username/password. Then go to Manage Linked Accounts, and click on the GitHub logo. This should take you through the GitHub auth process and make the association. Now go to My Roles and click the Refresh button to the right of the search box. NOTE: only public GitHub repos containing a meta/main.yml or ansible/meta.yml will appear on the list. Please update this issue, once you have been able to authenticate via a browser. |
No joy. I had tried this previously but did so in a completely different browser now with the same effect. Whenever I click on the Managed Linked Accounts link I get presented the same "Connect to Github" page like my accounts have never been linked before. I'm baffled at this point. |
At this point can my account be blown away completely and then I can start over? |
@chouseknecht can we just blow away @chris-short's account per his request? |
Same issue, but in my case I also have two accounts (not on purpose). Whenever I try to link my account and refresh it just asks me again. I wonder if it may be related to using multiple email addresses on GitHub. In my case I have two and I may have changed the primary at some point. Currently if I login using GitHub email verification tries to use my previous primary. EDIT: It solved itself a day later. Still have two accounts though. |
This issue was moved to ansible/galaxy#79 |
I have removed and re-added my authorization from GitHub but multiple scans have resulted in Galaxy not being able to find any roles for my account. I've been a Galaxy "user" for a long time and am wondering if something is afoot with my account.
Thanks,
Chris
The text was updated successfully, but these errors were encountered: