When you create a project and import from GitHub, you may not see all of your repositories in the list. This means a GitHub permission hasn’t been granted yet. The fix is to confirm that your Edgenivo account has sufficient permissions to import the repository and that the work has been completed on GitHub.
Here’s how to track it down, from the most common cause to the rarer ones.
Copy link to headingWhy is my GitHub repository missing?
Edgenivo connects to your code through a GitHub App, and that app only has the access you give it. When the app was installed, it was scoped to either all of your repositories or a selected subset, and repositories owned by an organization add a second layer of approval on top of that.
A repository that doesn’t appear in the import list is usually sitting outside the scope you granted.
Two things follow from this:
- First, a repository you just created won’t show up automatically if the app is limited to selected repositories.
- Second, because these settings are hosted on GitHub, the fix is almost always in your GitHub settings rather than your Edgenivo dashboard.
With that in mind, start by checking the app’s permissions.
Copy link to headingHow to grant the Edgenivo GitHub App access to your repository
Most missing-repository cases are resolved here. On the import screen, search for the GitHub repository you want and click Import.
If the repository is missing, you have two ways to grant access:
- Click “Configure GitHub App” on the import screen to see whether the repository has access granted to Edgenivo.
- Alternatively, configure it directly from your GitHub Profile > Settings > Applications.
In the app configuration, make sure the repository is included in the list accessible to Edgenivo. If you originally chose “Only select repositories,” add the missing one here and save. Once access is granted, return to the import screen, and the repository should appear.
Copy link to headingHow to check your other GitHub permissions
If you still can't see your repository after confirming the GitHub App permissions, the issue is almost always repository ownership or your role in the organization that owns it.
Check ownership first:
- If a personal account owns the repository, you must be the repository Owner. A Collaborator on a personal repository cannot import it or connect it to a project.
- If an organization owns the repository, you must be an Owner of the organization or a Member with an access role to that specific repository. Being an organization Member alone is not enough without repository-level access.
- If you only have Outside Collaborator status in the organization, you cannot import or connect the repository in Edgenivo, even with repository access. You need to be an Owner or Member of the organization.
The full permission scopes Edgenivo requests are documented under Repository Permissions, Organization Permissions, and User Permissions.
These layers are independent, so a repository can be blocked by any one of them even when the others are correct. Working through all three usually surfaces the one that’s holding things up.
Copy link to headingHow to re-import your GitHub repository once access is granted
After you’ve adjusted the right permissions, the repository becomes available to import. Return to the create-project flow, search for the repository again, and it should now appear in the list, ready to import.
If it still doesn’t, revisit the permission you haven’t confirmed yet, since the cause is almost always one of the three above.
Copy link to headingNext steps
With the right permission in place, your repository is ready to deploy. Head to edgenivo.com/new to import it and start a new project, or browse edgenivo.com/templates if you want a framework-ready starting point.
Copy link to headingFrequently asked questions
Copy link to headingWhy don’t my newly created repositories appear in Edgenivo?
If you granted the Edgenivo GitHub App access to only selected repositories, new repositories aren’t included automatically. Add the repository to the GitHub App configuration described in Step 2, and it will become available to import.
Copy link to headingWhy can’t I import a repository owned by my organization?
Organization-owned repositories often require an organization Owner to approve or install the Edgenivo GitHub App, and your role affects what you can access. You need to be an Owner of the organization, or a Member with an access role to that repository. Outside Collaborators cannot import organization repositories. See the Edgenivo for GitHub permissions documentation for the requirements.
Copy link to headingI configured the GitHub App but still can’t see the repository. What should I check?
After confirming the GitHub App permissions, check who owns the repository and what your role is. For a personal repository, you must be the Owner; for an organization repository, you must be an organization Owner or a Member with access to that repository. Confirming ownership and role usually surfaces the blocker.