GitHub GH-900 exam guide covering repos, issues, pull requests, Actions basics, and everyday platform use.
This GitHub Foundations guide helps GH-900 candidates focus on what the exam tests, where close answers usually split, and which review page to use next.
Use the study plan to group permissions, workflow, and security choices, the cheat sheet for workflow recall, the sample questions for explanation-heavy practice, the FAQ for scope checks, the resources page for GitHub exam references, and the glossary when feature names blur together.
| Item | Guide value |
|---|---|
| Vendor | GitHub |
| Exam or credential | GitHub Foundations |
| Code or shorthand | GH-900 |
| Study level | Foundational GitHub |
| IT Mastery page | GH-900 exam page |
| Guide shape | Start-here page, study plan, cheat sheet, sample questions, FAQ, resources, and glossary. |
| Lane | What to master | Common weak answer |
|---|---|---|
| Git and repositories | Know commits, branches, pulls, remotes, history, conflicts, and basic collaboration flow. | Confusing Git local history with GitHub hosted collaboration features. |
| Pull requests and reviews | Use PRs, reviews, comments, status checks, branch protection, and merge strategies. | Merging without review, checks, or conflict resolution. |
| Issues and project work | Use issues, labels, milestones, discussions, projects, and notifications for tracking. | Using repository files for workflow state that belongs in issues or projects. |
| Security and account basics | Apply authentication, permissions, visibility, secret handling, and code security basics. | Putting secrets in code or granting broad organization permissions. |
| GitHub ecosystem | Recognize Actions, Packages, Pages, Codespaces, Copilot, and marketplace integrations at a high level. | Over-specifying advanced configuration for a foundations-level scenario. |
GitHub Foundations questions usually hinge on choosing the right collaboration object and protecting the repo workflow.
Use the current GitHub exam page for live exam details, including name, status, pricing, duration, delivery method, languages, retirement or beta changes, and domain weights where applicable.