Migrating from GitHub.com to GitHub Enterprise
A practical guide to migrating repositories, teams, and CI/CD workflows from GitHub.com to a self-hosted GitHub Enterprise Server inside a private cloud network. Based on a real commercial migration — VM provisioning, networking nightmares, runner infrastructure, and hard-won troubleshooting lessons.
Unit 1
Why Migrate & Planning Your Approach
Understand the drivers behind a GHES migration and how to audit your existing GitHub.com footprint before you start.
Unit 2
Setting Up the GHES Virtual Machine
Provision the GHES VM on a private subnet, configure SSH admin access, TLS certificates, marketplace actions, self-hosted runners, and PATs.
Unit 3
Networking: The Hub-Spoke Firewall Gauntlet
The hardest part of a GHES migration. Hub-spoke traffic flows, Azure Firewall rules, service endpoints, private DNS zones, and why your ACI containers cannot reach 10.47.12.68 without careful configuration.
Unit 4
Migrating CI/CD Workflows
Step-by-step: rewriting GitHub Actions workflows for GHES — replacing marketplace actions, switching authentication, updating API URLs, and handling the self-signed certificate in every tool.
Unit 5
Real-World Pitfalls & Troubleshooting
A catalogue of the hardest bugs from the real migration — silent secret resolution, SSL handshake failures, orphaned ACI containers, resource group race conditions, and the OAuth route port problem.