Skip to main content

Migrate To GHE

This guide outlines the transition from code.connected.bmw to bmw.ghe.com (GitHub Enterprise Cloud).

To ensure a successful migration, follow the phases below. Most configuration must be handled manually by the Use Case Team, while the actual data move is performed by Orbit L2.

You will find dedicated migration guides here.

Phase 1: Pre-Migration (Action Required)​

Before Orbit L2 can move your data, the target environment must be ready.

  1. Create Org: Set up your organization on bmw.ghe.com. Note: Add Orbit L2 (Abhay-KA-Kumar, Chirag-Makkar, Satyajeet-Panigrahi) as Admins temporarily for the migration.
  2. Teams & Access: Recreate your team structures and assign roles.
  3. App & Secrets: Identify and reinstall required GitHub Apps. Recreate any Organization-level secrets and variables.

Phase 2: The Migration Process​

Once your Org is ready, coordinate the "Big Move" with the operations team.

  1. Schedule: Notify Orbit L2 in advance to coordinate the window.
  2. Lockdown: Repositories on the source (code.connected) will be locked to prevent data drift.
  3. Migration: Orbit L2 moves the repositories and updates Spaceship contracts.

Phase 3: Post-Migration & Validation​

After the repos appear on GHE, the Use Case Team must perform final manual configurations:

  1. Repo Settings: Add repository-level secrets, environments, and rulesets.
  2. Authentication: Replace SSH keys with GitHub Apps or Token-based auth.
  3. CI/CD: Install Spaceship Runners and verify workflows.
  4. Security: Enable GitHub Advanced Security (GHAS) if required.

Detailed Resources​