GitHub Verification
For applicants using GitHub Verification
Last updated
For applicants using GitHub Verification
Last updated
Open Source Collective offers the option to verify your project by showing that it meets our requirements. This can expedite the approval of your project.
If your project is not centered on a GitHub repository, or you can't get the automated verification system to work, please request instead.
There are a few possible causes for that:
#1: You may be using the wrong GitHub account in the authorization process
If you believe that you may have linked the wrong GitHub account to your Open Collective account, you will need to manually revoke access from the current linked GitHub profile. You can do that by either accessing or following our guide:
1. On GitHub, go to Settings.
2. On the Settings menu, click on Applications.
3. On the Applications page, open the Authorized OAuth Apps tab and look for Open Collective.
4. Click on the three dots on the right labeled "Show me more options" to revoke the authorization.
#2: You used the right account, but you didn't grant access to organization repositories
Use the search bar to filter repositories by name:
During the authorization process, GitHub lists the organizations in which you are a member. Depending on you have at each one of them and their , you may have to either grant permission on that page or request it.
Depending on you have at an organization, you may not be authorized to perform that action. Contact other members of your organization to discuss that process.
We agree the permissions are overly generous. Unfortunately, there's not much we can do at the moment since this is the only scope we can use to read the info we need. We've discussed this at length on issues , and .
If you have any suggestions on how to handle this better, feel free to join the discussions, start a new one, or send us an email .
