GH-900 Cheat Sheet 2026: Quick Reference
Every domain condensed to a table, plus a repository-files guide and a GitHub Copilot tier comparison the exam tests directly.
Exam Snapshot
We built this from Microsoft's published GH-900 skills outline, not a generic template — every reference link below points to the current Microsoft Learn page, verified before this went live.
1. Understand Git and GitHub Basics (25-30%)
| Concept | Area | Quick note |
|---|---|---|
| Version control purpose | Fundamentals | Why track changes at all |
| Git vs. GitHub | Fundamentals | Tool vs. the hosted platform built on it |
| Repositories, commits, branches | Fundamentals | The three core Git concepts |
| Accounts, organizations, enterprise | Working with GitHub | Different account structures for different scale |
| GitHub Flow | Working with GitHub | The standard branch-based collaboration workflow |
| Markdown in issues/PRs | Working with GitHub | Formatting for clear communication |
| GitHub Desktop vs. Mobile | Working with GitHub | Which client fits which use case |
2. Work with GitHub Repositories (10-15%)
| Concept | Area | Quick note |
|---|---|---|
| Repo structure & key files | Repository management | See the reference table below |
| Templates & branches | Repository management | Creating and organizing new repositories |
| Adding/managing files | Repository management | Basic file operations inside a repo |
| Repo insights, stars, metrics | Repository management | Visibility into repo health and activity |
| Dependency insights | Repository management | Supply-chain visibility for a repo |
3. Collaborate Using GitHub (10-15%)
| Concept | Area | Quick note |
|---|---|---|
| Issues, PRs, discussions | Collaboration tools | Three distinct collaboration surfaces, not interchangeable |
| Linking PRs to issues | Collaboration tools | Connecting a code change to a tracked item |
| Templates, filters, assignments | Collaboration tools | Structuring incoming work |
| Notifications | Collaboration tools | Configuring for workflow management, not just noise |
| Gists, Wikis, GitHub Pages | Collaboration tools | Three distinct ways to document and share |
4. Apply Modern Development Practices (10-15%)
| Concept | Area | Quick note |
|---|---|---|
| GitHub Actions | Automation | CI/CD and general workflow automation |
| GitHub Copilot | AI tools | AI-powered code suggestions, including agents and Agent Mode |
| Copilot tiers | AI tools | See the reference table below |
| GitHub Codespaces | Dev environments | Cloud dev containers, customizable |
| github.dev vs. Codespaces | Dev environments | Lightweight browser editor vs. a full dev environment |
5. Manage Projects with GitHub (5-10%)
| Concept | Area | Quick note |
|---|---|---|
| GitHub Projects & layouts | Project tracking | Boards, tables, and roadmap-style views |
| Labels, milestones, workflows | Project tracking | Organizing work items at scale |
| Saved replies & assignees | Project tracking | Streamlining repeated communication |
| Project insights | Project tracking | Tracking progress and productivity |
6. Understand Privacy, Security, and Administration (10-15%)
| Concept | Area | Quick note |
|---|---|---|
| 2FA & passkeys | Account security | Securing sign-in beyond a password |
| Access permissions & roles | Access management | Repo- and org-level role distinctions |
| Enterprise Managed Users (EMUs) | Access management | Org-controlled identities, not personal accounts |
| Org-wide Copilot policy | Access management | Central AI governance across an organization |
| Repo privacy & visibility | Access management | Who can see a repository at all |
| Branch protection rules | Access management | Preventing unreviewed changes from merging |
Common Mistake: Treating Branch Protection as Optional
The security table above lists branch protection rules almost in passing, but skipping them is one of the most common real-world GitHub mistakes. Without a protection rule on the default branch, any collaborator with write access can push straight to main, bypassing pull request review entirely — even if the team's workflow assumes every change goes through GitHub Flow. A single unreviewed push can overwrite a teammate's work or rewrite commit history outright. Turning on required reviews and status checks for the default branch is what actually makes the collaboration tools in the table above (issues, PRs, linked reviews) mean anything — they only matter if merging without them isn't just as easy.
7. Explore the GitHub Community (5-10%)
| Concept | Area | Quick note |
|---|---|---|
| Open source benefits & GitHub Sponsors | Community | The value case for open source plus how funding works |
| Following users/orgs | Community | Staying informed about activity |
| GitHub Marketplace | Community | Discovering apps and Actions built by others |
| InnerSource | Community | Applying open-source principles inside a single organization |
| Forks, templates, discoverable repos | Community | Mechanisms that promote collaboration |
Repository Special Files Quick Reference
| File | Purpose |
|---|---|
| README | Project overview and getting-started info |
| LICENSE | Legal terms for using and distributing the code |
| CONTRIBUTING | How to propose changes to the project |
| CODEOWNERS | Who is automatically requested to review specific paths |
| SECURITY | How to report a vulnerability responsibly |
GitHub Copilot Tier Quick Reference
| Tier | Best fit |
|---|---|
| Individual | A single developer, personal projects |
| Business | A team or org needing centralized billing and policy control |
| Enterprise | Large orgs needing EMU integration and org-wide governance |
GH-900 Quick Answers
How is this cheat sheet different from the GH-900 study guide?
The study guide explains each domain in narrative form with a study plan. This page is tables only, for a final scan before the exam.
What are the required files in a well-structured GitHub repository?
README, LICENSE, CONTRIBUTING, CODEOWNERS, and SECURITY — each with a distinct purpose. See the table above.
What's the difference between Copilot Individual, Business, and Enterprise?
Individual fits one developer. Business adds centralized billing and policy control. Enterprise adds EMU integration and org-wide governance.
Can I print this GH-900 cheat sheet?
Yes — every table here is plain HTML, so a browser print or "print to PDF" renders cleanly.
MSCertQuiz sells practice-exam access for GH-900 and other Microsoft certifications; this cheat sheet is written by the same team that builds those questions.
Where to Go Next
The 3-week plan behind this quick reference.
Scenario questions with detailed explanations.
Browse every Microsoft certification MSCertQuiz covers.
Full exam details and the complete practice bank.
Reviewed the cheat sheet? Now drill it.
Start with free GH-900 questions covering every domain above.
Start Free GH-900 Practice