GitHub Foundations (GH-900) and Git Essentials Exam Prep
Revise the seven GH-900 domains, from Git commits and branches to pull requests, Projects, Actions, Copilot, Codespaces, security and open source, with original exam-style questions.
What you will learn
- Describe the GH-900 exam, explain version control and use core Git concepts: repositories, commits, branches, merges and remotes.
- Distinguish Git from GitHub, choose the right account type, follow the GitHub Flow and write clear Markdown in issues and pull requests.
- Create, structure and maintain repositories with key files, templates, branches and repository insights.
- Collaborate with issues, pull requests, discussions and notifications, and share information with Gists, wikis and GitHub Pages.
- Explain what GitHub Actions, GitHub Copilot, Codespaces and the github.dev editor do and choose the right one for a task.
- Plan and track work with GitHub Projects, labels, milestones, saved replies, built-in workflows and insights.
- Secure accounts and repositories with 2FA, passkeys, roles, visibility settings, branch protection and organization policies.
- Take part in the GitHub community: open source, forks, Sponsors, Marketplace, following, discoverability and InnerSource.
Modules
- The GH-900 exam and Git fundamentals
- GitHub, accounts, GitHub Flow and Markdown
- Working with GitHub repositories
- Collaborating on GitHub
- Modern development: Actions, Copilot, Codespaces and github.dev
- Managing projects with GitHub
- Privacy, security and administration
- The GitHub community and open source
Course facts
- Level
- Exam preparation
- Estimated study time
- about 2 hours
- Final assessment
- 50 questions · Pass mark 70%
- Available in
- English, Français, العربية
- Price
- Free. Optional verifiable certificate: $5
- Last updated
- Published by
- AMAADOR ACADEMY
Who this course is for
Students, junior developers, project managers, technical writers, designers and IT staff who use GitHub and want to pass Microsoft exam GH-900: GitHub Foundations, or simply learn Git and GitHub properly.
Prerequisites
None required. A free GitHub account helps: you can try every feature in this course on your own test repository. No programming experience is needed; the exam is designed for non-developers as well as developers.
Course content
1. The GH-900 exam and Git fundamentals
GitHub Foundations is the entry-level GitHub certification, now delivered through Microsoft Learn. The facts below come from the Microsoft Learn certification page and the GH-900 study guide (skills measured as of January 2026), checked in November 2026.
| Item | What Microsoft Learn states |
|---|---|
| Exam | GH-900: GitHub Foundations, level Beginner |
| Time | 100 minutes, proctored, through Pearson VUE |
| Passing score | 700 or greater (scaled score) |
| Languages | English, Spanish, Portuguese (Brazil), Korean, Japanese |
| Renewal | Not required (fundamentals-level policy) |
| Practice | Free practice assessment and an exam sandbox |
| Domain | Weight | Module |
|---|---|---|
| Git and GitHub basics | 25-30% | 1-2 |
| Work with repositories | 10-15% | 3 |
| Collaborate using GitHub | 10-15% | 4 |
| Modern development practices | 10-15% | 5 |
| Manage projects | 5-10% | 6 |
| Privacy, security, administration | 10-15% | 7 |
| GitHub community | 5-10% | 8 |
The price depends on the country where you sit the exam and is shown when you schedule. The study guide says the outline changed significantly in January 2026, so avoid older material.
Why version control?
Version control records every change to a set of files: who changed what, when and why. You can compare versions, go back to a working state and let several people work in parallel without overwriting each other. It is useful for documents, configuration and data scripts, not only code.
2. GitHub, accounts, GitHub Flow and Markdown
| Git | GitHub |
|---|---|
| Version control software you install | Cloud platform that hosts Git repositories |
| Works offline on your computer | Accessed through the web, apps, CLI and API |
| Tracks commits, branches, merges | Adds issues, pull requests, Actions, Copilot, Projects, security features |
| Open source, maintained by the Git project | Product of GitHub, Inc., a Microsoft subsidiary |
You can use Git without GitHub, and other hosts exist. GitHub uses Git underneath: a GitHub repository is a Git repository with a web interface and collaboration tools around it.
Three kinds of account
- Personal account — your identity on GitHub. Each person has one, owns its repositories and can be a member of many organizations. Plans include GitHub Free and GitHub Pro.
- Organization — a shared account where many people collaborate. Owners manage members, teams, repository access and billing. Plans include GitHub Free for organizations, GitHub Team and GitHub Enterprise.
- Enterprise account — available with GitHub Enterprise; it groups several organizations and applies policies, auditing and billing centrally.
GitHub Enterprise can run as GitHub Enterprise Cloud (hosted by GitHub) or GitHub Enterprise Server (self-hosted by the customer). With Enterprise Cloud, a company can choose Enterprise Managed Users, where accounts are created and controlled by its identity provider (covered in module 7).
3. Working with GitHub repositories
| File | Purpose |
|---|---|
| README.md | What the project is, how to install and use it. Shown on the repository home page. |
| LICENSE | The legal terms for reuse. Without a licence, default copyright applies and others have no clear right to reuse the code. |
| CONTRIBUTING.md | How to propose changes: branch naming, tests, style, review process. |
| CODEOWNERS | Maps paths to people or teams who are automatically requested for review. Placed in the root, docs/ or .github/ folder. |
| SECURITY.md | How to report a vulnerability privately and which versions are supported. |
| CODE_OF_CONDUCT.md | Expected behaviour in the community. |
| .gitignore | Files Git must not track. |
Several of these can live in a special .github repository of an organization to act as defaults for all its repositories, such as community health files and issue templates.
Creating and organizing
- When you create a repository you choose owner, name, visibility, and optionally a README, .gitignore template and licence.
- A template repository lets others generate new repositories with the same files and folders. The new repository starts with a fresh, unrelated history; it is not a fork.
- Topics and a clear description help people find and classify repositories.
4. Collaborating on GitHub
| Tool | Use it for | Key features |
|---|---|---|
| Issue | A unit of work: bug, task, feature idea | Assignees, labels, milestones, sub-issues, issue types, templates and forms |
| Pull request | Proposing and reviewing a change from one branch into another | Diff, review comments, approvals, requested changes, status checks, draft mode |
| Discussion | Open conversation: questions, ideas, announcements, polls | Categories, Q&A with a marked answer, upvotes, can be converted to an issue |
Linking pull requests to issues
Write a closing keyword followed by the issue reference in the pull request description: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved. Example: Closes #12. The issue closes when the pull request is merged into the default branch. You can also link manually from the Development section of the pull request or issue.
Templates, filters and assignments
- Issue templates and issue forms live in .github/ISSUE_TEMPLATE; a pull request template is pull_request_template.md, often in .github.
- Filters such as is:open is:issue label:bug assignee:@me find work fast.
- Assignees show who is responsible; reviewers are requested on pull requests.
5. Modern development: Actions, Copilot, Codespaces and github.dev
GitHub Actions
GitHub Actions automates tasks in response to events. Typical uses: build and test every pull request (CI), deploy after a merge (CD), label new issues, or publish a package on release.
| Term | Meaning |
|---|---|
| Workflow | A YAML file in .github/workflows that defines the automation |
| Event | What triggers it: push, pull_request, schedule, manual run, issue opened |
| Job | A set of steps that runs on one runner |
| Step | A command or a reusable action |
| Action | A reusable unit, often from GitHub Marketplace |
| Runner | The machine that runs the job: GitHub-hosted or self-hosted |
GitHub Copilot
Copilot is GitHub’s AI assistant. It offers code completions in the editor, Copilot Chat for questions and explanations, and agent features:
- Agent mode in the IDE — Copilot plans and makes multi-file edits, runs commands and iterates until the task is done, with you approving.
- Copilot coding agent — you assign an issue to Copilot on GitHub; it works in the background and opens a pull request for human review.
- Multi-model support — depending on the plan and policy, you can choose among several AI models from different providers.
6. Managing projects with GitHub
A project is an adaptable planning surface owned by a user or an organization. It holds issues, pull requests and draft items, and can pull items from many repositories. Changes stay in sync: closing an issue updates the project.
| Layout | Best for |
|---|---|
| Table | A spreadsheet-style list to sort, filter, group and edit fields in bulk |
| Board | A kanban view with columns, usually by Status |
| Roadmap | A timeline based on date or iteration fields |
You can save several views of the same project, each with its own layout, filter, sort and grouping, for example one board per team.
Custom fields
- Text and number — notes, estimates, story points
- Date — start and target dates
- Single select — Status, Priority, Team
- Iteration — repeating time blocks such as two-week sprints, with optional breaks
Built-in workflows and automation
- Item closed — set Status to Done automatically.
- Pull request merged — set Status to Done.
- Auto-add — add new issues that match a filter from a repository.
- Auto-archive — archive items that match criteria, to keep the project light.
7. Privacy, security and administration
Two-factor authentication (2FA) asks for something you have in addition to your password. GitHub has required 2FA for accounts that contribute code on GitHub.com, and organization owners can require it for all members.
| Method | Notes |
|---|---|
| Authenticator app (TOTP) | Recommended baseline; codes generated on your phone |
| Security key or passkey | Phishing-resistant; works with WebAuthn |
| GitHub Mobile | Approve sign-in prompts on your phone |
| SMS | Available in some countries; weakest option |
A passkey lets you sign in without typing a password, using your device’s fingerprint, face or PIN. Because it is bound to the real site, it resists phishing, and it satisfies both factors at once. Always download and store your recovery codes safely: without them, losing your phone can mean losing the account.
Enterprise Managed Users (EMU)
With GitHub Enterprise Cloud, a company can use Enterprise Managed Users. User accounts are provisioned, updated and suspended from the company’s identity provider, such as Microsoft Entra ID or Okta, and people sign in through it. Managed users cannot create public content or contribute to repositories outside the enterprise. The company controls usernames, profile data and access centrally.
8. The GitHub community and open source
Open source software publishes its source code under a licence that lets anyone use, study, change and share it. Benefits include transparency, shared maintenance, faster innovation and the chance for people to learn and build a public portfolio.
How GitHub supports open source
- Free public repositories with issues, pull requests, Actions and Pages.
- Community health files: README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY.
- Labels such as good first issue and help wanted to guide newcomers.
- Security features such as Dependabot alerts and private vulnerability reporting.
Contributing with a fork
- Fork — create your own copy of the repository, linked to the original (upstream).
- Branch and commit — make the change in your fork.
- Open a pull request — from your fork’s branch to the upstream repository.
- Respond to review — maintainers decide whether to merge.
- Sync — keep your fork up to date with the upstream branch.
GitHub Sponsors
GitHub Sponsors lets people and organizations fund the developers and projects they depend on, through monthly or one-time sponsorships with tiers chosen by the maintainer. A FUNDING.yml file adds a Sponsor button to a repository.
The full lesson continues in the interactive course on this page.
Sources and references
- Study guide for Exam GH-900: GitHub Foundations
- GitHub Foundations certification page
- Get started with GitHub
- Pull requests documentation
- Planning and tracking with Projects
- Authentication and account security
- Pro Git book (official Git documentation)
- Reported supply chain compromise affecting XZ Utils (CVE-2024-3094)
- Uber agrees to expanded settlement with FTC related to privacy, security claims (April 2018)
Unofficial practice course. Not affiliated with, endorsed by or sponsored by GitHub, Inc. or Microsoft. GitHub Foundations and GH-900 are trademarks of their owner. All questions are original and are not real exam items. GitHub features and plan names change often. Check the current exam outline on Microsoft Learn before you book.
All courses · DevOps & Platform Engineering — Free certified training | AMAADOR ACADEMY