Skip to main content
Migrating to GitHub Cloud App Pro replaces your existing GitHub App installation with the Pro version. To preserve your current projects and findings, select the same repositories you were scanning before.
Before you begin, confirm that a GitHub organization admin can approve the installation request for GitHub Cloud App Pro. If no admin approves it, all scans, including PR scans, fail until the request is approved.
To migrate to GitHub Cloud App Pro:
  1. Select User menu > Integrations from the left sidebar.
  2. Click Manage next to GitHub under Source Control Managers.
  3. Click the vertical three dots next to the integration you want to migrate and select Migrate to Pro App.
  4. Click Migrate. You are redirected to GitHub.
  5. Click Configure.
  6. Select a user to authorize the app.
  7. Select Configure in the organization where you want to migrate the app.
  8. Choose whether to install and authorize Endor Labs on all repositories or a specific subset.
  9. Choose the namespace and click Next.
    You must choose the same namespace as your existing GitHub App installation.
  10. Select and enable the scanners you require.
  11. Configure pull request scanning preferences if required.
  12. Click Continue.
Keep the old installation until the organization syncsDon’t uninstall the standard GitHub App until migration is complete and Endor Labs has synced the organization at least once after the migration. Uninstalling it earlier deletes your existing projects and permanently removes their scan history.To confirm that the sync is complete:
  1. Select User menu > Integrations from the left sidebar.
  2. Click Manage next to GitHub under Source Control Managers.
  3. Check the Last Scanned status of your integration. A recent timestamp confirms that the new integration has scanned your repositories.
Once the organization has synced after the successful migration, delete the old installation from your GitHub organization.
Branch protection rulesWhen you migrate from one app to another, you must manually update your branch protection rules in GitHub. Branch protection rules that reference the old GitHub App ID will become inactive and will not function until reconfigured with the new app. Refer to Branch protection rules to learn more.