Onboarding Checklist: GitHub Enterprise

Before configuring anything, establish what good looks like for your org.

Map how orgs, teams, and roles connect to your development topology.

Configure enterprise-level policies, connect billing, register support entitlements, and finish your IAM configuration.

Select and migrate pilot teams or repositories to GitHub.

Admins should complete the GitHub Administration Learning Path to build platform confidence.

Provide role-specific training so developers can self-serve from day one.

Identify champions to lead an internal space where developers can ask questions and crowdsource help.

Have champions lead the pilot team through their first issues and pull requests to build familiarity before the broader rollout.

Replace manual per-repo configuration with centrally managed rulesets to bring consistency to branching and merge requirements.

Use repository templates and custom properties so new repos are created with built-in standards as the enterprise scales.

Set up streaming to your SIEM or data platform so compliance and security teams have continuous, queryable access to enterprise activity.

Define who reviews what, what checks must pass, and how teams collaborate on code changes. PR workflow maturity is a strong signal of platform depth.

Before expanding, gather structured feedback from champions and users. Run a short retrospective prior to every subsequent rollout wave.

You created a repeatable process with the pilot and then laid the governance foundation in Week 3. Apply both to bring the next wave of teams onto GitHub faster. Use the runbooks, repository templates, and rulesets already in place.

Document and present what the pilot teams accomplished with the community hub and leadership; rallying around migrations completed, first PRs merged, and developer feedback builds momentum.

Review signals like seat activation, PR activity, and community discussion volume to monitor progress and inform defining specific expansion targets for the next period.