Review GitHub Foundations (GH-900) Git basics, repositories, branches, pull requests, issues, projects, security, and collaboration traps before practicing in IT Mastery.
GH-900 is a foundations exam, so most questions test whether you recognize the GitHub object, workflow step, or permission boundary. Use this cheat sheet to review the core vocabulary before a free diagnostic or timed practice.
Use this with practice. Review the GitHub workflow basics, then take the free GH-900 diagnostic or open the full Foundations route in IT Mastery.
| Field | Detail |
|---|---|
| Vendor | GitHub |
| Credential name | GitHub Foundations |
| Exam code | GH-900 |
| Level shown by Microsoft Learn | Beginner |
| Exam time shown by Microsoft Learn | 100 minutes |
| IT Mastery status | Live GH-900 practice available |
| Area | What to know | Common trap |
|---|---|---|
| Git and GitHub basics | Repositories, commits, branches, remotes, clone, push, pull, and merge | Confusing local Git actions with GitHub collaboration features |
| Repositories | Files, README, issues, pull requests, discussions, releases, visibility, and settings | Treating a repository as only a file folder |
| Collaboration | Forks, branches, reviews, comments, checks, merge readiness, and contribution flow | Opening direct changes when a pull request is expected |
| Modern development | Projects, GitHub Pages, packages, Codespaces awareness, and community workflows | Choosing a tool because it sounds related, not because it fits the workflow |
| Security and administration | 2FA, roles, repository visibility, branch protection, organizations, and permissions | Giving admin access for work that only needs write or maintain access |
| Distinction | How to decide |
|---|---|
| Git vs GitHub | Git is version control; GitHub hosts repositories and collaboration workflows. |
| Commit vs pull request | A commit records changes; a pull request proposes changes for review and merge. |
| Branch vs fork | A branch is a line of work in a repository; a fork is a copy under another account or organization. |
| Issue vs pull request | Issues track discussion or work; pull requests contain proposed code changes. |
| Discussion vs issue | Discussions support open-ended conversation; issues track actionable work or bugs. |
| Release vs tag | A tag marks a version in Git; a GitHub release adds release notes and assets around a tag. |
| Read vs write vs admin | Read can view, write can contribute, admin can manage repository settings and high-risk controls. |
| Public vs private vs internal | Public is visible to everyone; private is restricted; internal is visible within an enterprise context. |
Take the free GH-900 diagnostic and tag each miss by object type: Git, repository, issue, pull request, project, security, or community. Then drill the matching topic page before returning to mixed practice.
Because GH-900 is a foundations route, avoid memorizing interface labels without context. The right answer usually follows from the workflow: branch, commit, push, open pull request, review, fix checks, merge, and release.