-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-scan for non picked-up Github accounts #106
Comments
That's a good idea. |
wrong forum. |
Also some keys seem to have been incompatible, a re-scan with warning beforehand would be awesome ❤️ |
Some people (including myself) may have deleted old security keys for security reasons. Please do a rescan. |
Rescan |
1 similar comment
Rescan |
If you want a rescan use the proposal that's been made : https://gov.fluence.network/t/re-scan-for-non-picked-up-github-accounts/230/2 |
重新扫描 |
I'm wondering if a re-scan might help my issue. The website says that I am eligible but metadata.bin says not. |
"The rejection of OAuth usage is justified, as depicted in the Medium article; however, many developers, for various reasons, did not have an SSH key at the time of the snapshot, excluding them entirely from the distribution.
To my knowledge, no warning was given beforehand, making this situation frustrating for many of us.
Why not perform another scan for accounts not picked up in a few days?
The text was updated successfully, but these errors were encountered: