GitHub Foundations Exam Guide: Skills, Study Plan, and Scheduling Decisions
GitHub Foundations validates beginner-level knowledge of GitHub concepts, products, and ways of collaborating, contributing, and managing work on the platform. It serves non-developers, developers, administrators, and other GitHub users who need a reliable foundation rather than a specialist credential. This guide helps you decide whether your current experience is sufficient, which exam domains need the most study time, how to practise without relying on leaked content, and when to move from learning to scheduling Exam GH-900.
What the GitHub Foundations certification validates
GitHub Foundations confirms that you understand the core ideas behind using GitHub: version control, repositories, collaboration, project management, modern development practices, privacy, security, administration, and the GitHub community. It is a foundation-level assessment, so preparation should focus on recognising the purpose and appropriate use of GitHub features rather than mastering advanced software engineering.
The intended audience
Microsoft describes the certification as suitable for non-developers, developers, and GitHub users who want to improve their proficiency with GitHub fundamentals. The certification page associates it with Administrator, App Maker, Developer, DevOps Engineer, and Solution Architect roles. That range makes it useful for people who participate in software work without all performing the same technical job.
What the certification does not establish
Passing does not by itself demonstrate that you can design a production system, administer a large enterprise, write complex code, or operate every GitHub product. The official audience profile calls for foundational knowledge. Treat the credential as evidence that you understand the platform’s vocabulary, workflows, and major capabilities, not as a substitute for role-specific experience.
Check the current exam identity and blueprint
The associated assessment is Exam GH-900: GitHub Foundations. Start with the current Microsoft Learn study guide before building a revision plan, because the guide identifies the skills measured and notes that the outline can change. The January 2026 outline is the relevant blueprint represented in the supplied official research.
Exam domains and official weights
As of the January 2026 skills outline, Understand Git and GitHub basics represents 25–30% of the GH-900 exam; Work with GitHub repositories represents 10–15%; Collaborate using GitHub represents 10–15%; Apply modern development practices represents 10–15%; Manage projects with GitHub represents 5–10%; Understand privacy, security, and administration represents 10–15%; and Explore the GitHub community represents 5–10%.
How to use the ranges
The ranges are planning signals, not a promise about the exact distribution on your appointment. Give the largest deliberate block to Understand Git and GitHub basics, then cover the five domains with 10–15% or 5–10% ranges according to your weaknesses. Do not interpret a smaller official range as permission to skip a domain; a gap in a smaller area can still cost marks and expose weak understanding.
What the study guide means by assessed skills
The study guide says that the bullets under each skill illustrate how Microsoft assesses that skill and that related topics may also be covered. It also notes that most questions address generally available features, although preview features may appear when they are commonly used. Use the blueprint to set boundaries, but learn the underlying purpose of a feature rather than memorising an isolated label.
Decide whether you are ready to start preparation
You are ready to begin focused preparation if you can explain how Git and GitHub differ, describe what a repository contains, follow the logic of a branch and pull request, and identify where issues, discussions, projects, and security controls fit. If those terms are familiar only as menu labels, begin with the learning path instead of jumping directly to practice questions.
A practical self-check
Write a short explanation, without opening reference material, of how a change moves from a local or hosted working copy into a collaborative review. Then explain how a project item differs from a repository issue, why access permissions matter, and where a user would look for community or product guidance. Any answer that depends on guessing should become a study task.
When hands-on work is worth the time
Use a small personal repository to connect concepts that are easy to confuse in theory. Create a branch, make a commit, open a pull request, and inspect the review workflow. Add an issue, place work in a project, and practise writing a clear Markdown description. The purpose is not to simulate confidential exam content; it is to make the relationships among features memorable.
Separate experience from exam readiness
Frequent GitHub use helps, but routine activity can leave blind spots. Someone who only opens pull requests may know collaboration well while missing account types, repository visibility, security features, or community resources. Conversely, someone who has studied terminology may still struggle to choose the correct workflow. Test both recognition and explanation before scheduling.
Build the foundation before the feature catalogue
Study version control and the GitHub model before moving into specialised products. The official learning path begins with Introduction to Git and Introduction to GitHub, then covers GitHub products, code scanning, GitHub Copilot, Codespaces, Projects, and Markdown. That sequence gives you a usable mental model before you memorise where individual capabilities belong.
Stage one: Git and version control
Learn why version control records change over time, then distinguish Git, the version control system, from GitHub, the platform that supports hosting, collaboration, and related services. Be comfortable with repositories, commits, and branches. You should be able to describe the role of each object and explain why a team would isolate work before merging it.
Stage two: the GitHub collaboration loop
Connect branches, commits, pull requests, reviews, issues, notifications, and Markdown into one workflow. The official course describes GitHub Flow, branches, commits, pull requests, issues, discussions, notifications, and subscriptions as part of its coverage. Study these as decisions in a process: propose work, make a change, communicate context, review it, and track what remains.
Stage three: products and working environments
After the core workflow is clear, review GitHub account types, plan options, and associated features, as well as GitHub Desktop and GitHub Mobile. The learning path also introduces code scanning, GitHub Actions, GitHub Copilot, Codespaces, Projects, and Markdown. For each product or capability, record its primary purpose, its relationship to repository work, and the problem it solves.
Use the repositories domain to connect configuration with work
Repository knowledge is more than knowing how to create one. Prepare to reason about how repository structure, files, branches, commits, visibility, and contribution settings support a project. When studying a repository feature, ask what it controls, who benefits from it, and how it affects the path from an individual change to shared work.
A useful repository exercise
Create a harmless practice repository and document its purpose in Markdown. Make a branch for a small change, commit a meaningful update, and compare the branch with the default line of work. Open a pull request and inspect the information presented to collaborators. This exercise reinforces the difference between storing code, recording change, and proposing change.
Repository mistakes to avoid
Do not treat a repository as a project-management board, and do not assume that every collaboration problem is solved by changing branch names. Do not study visibility or access as abstract vocabulary only. Relate those settings to who can view, contribute to, review, or administer work, while checking the current official material for the exact feature behaviour.
Practise collaboration as a sequence of decisions
The collaboration domain is easiest to learn when each feature has a clear job. Issues can communicate and track work, pull requests can propose changes for review, discussions can support broader conversation, and notifications help users follow activity. Practise choosing the suitable mechanism for a situation instead of memorising that all of them are simply communication tools.
Questions to ask for every collaboration feature
Ask whether the item is primarily for a change, a task, a question, a conversation, or an alert. Then ask who needs to act, what context should be retained, and how the item relates to repository history. This framing helps you distinguish a pull request from an issue and an issue from a discussion without relying on superficial interface similarities.
Markdown is part of effective collaboration
The study guide includes Markdown uses for clear communication in issues and pull requests, and the learning path includes a dedicated Markdown module. Practise headings, lists, links, code formatting, and concise descriptions in a test repository. The goal is readable context: a reviewer should be able to understand the requested change and its status quickly.
Notifications need deliberate practice
Review how notifications and subscriptions support collaboration, as these are specifically mentioned in the official course description. Consider the difference between being involved in an item and receiving updates about it. Configure a practice workflow, observe which activities generate notifications, and write down the control you would investigate when updates become too broad or too limited.
Cover modern development practices without chasing every tool
Modern development practices in this exam include capabilities introduced through the official learning path, including code scanning, GitHub Actions, GitHub Copilot, and Codespaces. Study the purpose and position of each capability in a development workflow. Foundation-level preparation should explain what a tool is for and when it is relevant, not attempt to become an advanced implementation course for every product.
Code scanning and GitHub Actions
The learning path introduces code scanning through CodeQL, third-party tools, and GitHub Actions. Build a simple comparison note: code scanning identifies potential code problems, while Actions provides an automation mechanism that can run workflows. Do not collapse the two into one feature. Learn how automation can be involved in scanning and why the underlying objectives remain distinct.
Copilot and Codespaces
The official learning path describes GitHub Copilot as an AI-powered coding assistant that can help generate, understand, refactor, and debug code through inline suggestions and chat. It describes Codespaces as a fully configured development environment hosted in the cloud. Remember these as different capabilities: one assists with coding and the other supplies a development workspace.
A responsible study boundary
Avoid building revision around claims about what an AI assistant will always produce or how a particular preview feature behaves. The study guide says most questions cover generally available features and may include commonly used preview features. Confirm current product information in Microsoft Learn, and focus on stable concepts, terminology, intended use, and safe distinctions among services.
Study GitHub Projects as work tracking, not just a board
Projects belongs to the project-management portion of the blueprint, and the learning path describes creating issues, breaking them into tasks, tracking relationships, adding custom fields, and having conversations. Practise translating a broad outcome into trackable work, then connect that work to repository activity. This makes project-management questions concrete rather than purely interface-based.
A small project exercise
Create a practice project for a documentation improvement. Add an issue for the outcome, divide it into tasks, and identify relationships among the items. Add a custom field that helps you sort or classify work, then record a short conversation about a decision. The exercise should teach you why a project adds planning context around repository work.
Common project-management confusion
Do not assume that an issue, a task, a project item, and a pull request are interchangeable. They can be related, but they represent different kinds of work and evidence. When revising, draw the relationships on paper and explain what would remain visible if the code change, discussion, or planning record were considered separately.
Treat privacy, security, and administration as operational choices
Privacy, security, and administration require more than remembering feature names. Prepare to reason about who should access information, who may change settings, and how a team protects or governs its work. Tie each study note to a practical question about visibility, permissions, account or organisation management, and security controls, then verify details against current Microsoft Learn material.
Use role-based reasoning
For each administrative or security concept, ask which actor needs the capability and what risk or operational need it addresses. A contributor, repository administrator, organisation owner, and enterprise stakeholder may not have the same responsibilities. This approach is safer than assuming that the person who can edit code can also change every repository or organisational setting.
Avoid overgeneralising plans and permissions
The learning path covers account types, plan options, and associated features, while the study guide provides the exam boundary. Plan names and feature availability can change, so do not rely on an old comparison table or an unofficial summary. Check the current official documentation when a question depends on a particular plan, permission, or administration detail.
Use the GitHub community domain to round out the blueprint
The community domain is smaller than the Git and GitHub basics domain, but it still belongs in the study plan. Learn how GitHub users find, share, and participate in the wider community surrounding the platform and open-source work. The safest preparation is to understand the purpose of community resources and responsible participation rather than memorising names without context.
A focused review method
Reserve a short final review for community concepts after the larger workflow domains are stable. Write down where you would seek product guidance, how you would communicate a question clearly, and how community participation differs from changing a repository. This prevents the smaller domain from disappearing while keeping it proportionate to the official 5–10% range.
Choose Microsoft Learn resources that match your study style
Microsoft provides a GitHub Foundations learning path, a GH-900T00-A course, an exam sandbox, a practice assessment, and the GH-900 study guide. Use the study guide as the authority for scope, the learning path for structured self-study, the course for a guided option, and the sandbox and practice assessment for exam preparation and readiness checks.
The learning path
The GitHub Foundations Part 1 of 2 learning path contains 8 modules and is described as a beginner-friendly introduction to GitHub concepts and products. Its modules cover Git, GitHub features and products, code scanning, Copilot, Codespaces, Projects, and Markdown. Work through it actively: pause to perform the exercises or reproduce the workflow in a practice repository.
The instructor-led or self-paced course
Microsoft lists GH-900T00-A: GitHub Foundations as a two-day course and states that preparation can be instructor-led or self-paced. Choose the guided route if you need a fixed sequence, explanations, and scheduled study time. Choose self-paced learning if you can maintain a checklist and regularly test yourself instead of passively reading modules.
The official practice assessment
Use the practice assessment after your first pass through the domains. Microsoft says practice assessments provide an overview of the style, wording, and difficulty candidates are likely to experience, while also helping identify knowledge gaps. Review every uncertain answer, not only incorrect answers, and turn recurring gaps into targeted revision rather than repeatedly retaking the assessment without analysis.
The exam sandbox
Microsoft Learn provides an exam sandbox where candidates can experience the exam interface and interact with the question types used in the exam. Use it before the appointment so the interface is not a new variable on the day. The sandbox is for familiarisation with the environment, not a source of live or confidential exam questions.
Follow a four-phase study roadmap
A workable roadmap has four phases: establish the Git and GitHub model, practise the collaborative workflow, cover products and governance, and validate readiness against the blueprint. The exact calendar should reflect your starting knowledge. Keep a written gap list so extra study time goes to weak domains instead of being spent rereading topics you already explain confidently.
Phase one: establish the vocabulary
Begin with version control, Git, GitHub, repositories, commits, branches, accounts, organisations, and the basic collaboration flow. Make a one-page concept map and explain it aloud. If you cannot describe the difference between a commit, a branch, and a pull request without opening notes, do not progress to product-specific revision yet.
Phase two: perform the workflow
Use a practice repository to create a branch, make a commit, open a pull request, and review the surrounding communication. Add an issue and a project item, then use Markdown to record the objective and status. Your notes should answer what happened, where it was recorded, and which feature a collaborator would use next.
Phase three: cover modern practices and governance
Study code scanning, Actions, Copilot, Codespaces, Projects, privacy, security, administration, and community topics. For each, write a purpose statement and one distinction from a nearby feature. Recheck current Microsoft Learn content for plan-dependent or preview-related details instead of treating a third-party summary as authoritative.
Phase four: measure and repair gaps
Take the official practice assessment under focused conditions, inspect the report, and map each uncertain area to an exam domain. Revisit the relevant Microsoft Learn module or study-guide topic, then explain the concept in your own words and apply it in a safe hands-on exercise where appropriate. Repeat the diagnostic process only after repairing the identified gaps.
Allocate revision time according to the blueprint and your gaps
Use the official ranges to prevent an attractive topic from consuming the entire plan. Understand Git and GitHub basics has the largest range at 25–30%, while Work with GitHub repositories, Collaborate using GitHub, Apply modern development practices, and Understand privacy, security, and administration each have a 10–15% range. Manage projects with GitHub and Explore the GitHub community each have a 5–10% range.
A practical prioritisation rule
Start with the official weighting, then adjust for demonstrated weakness. For example, a developer may need less introductory Git practice but more work on administration and community concepts; a project coordinator may need the opposite balance. This is a recommendation, not an official scoring formula. The official source provides ranges, not a guarantee of marks by individual topic.
Keep a domain evidence table
Create seven rows, one for each official domain, with columns for terms recognised, workflow explained, hands-on task completed, and practice-assessment evidence. A domain is not ready merely because you have read it. Mark it ready when you can explain its purpose, distinguish it from related features, and answer scenario-style prompts without guessing.
Avoid preparation habits that create false confidence
The most damaging preparation mistake is confusing exposure with understanding. Reading a feature description, memorising an unofficial question set, or repeatedly choosing familiar answers does not prove that you can apply the GitHub model. Use official scope, active recall, and simple workflows to test comprehension while avoiding dumps, leaked questions, and claims that memorisation guarantees a pass.
Do not study only the largest domain
The 25–30% range for Understand Git and GitHub basics makes it a priority, but the other six domains still form the rest of the blueprint. Skipping privacy, security, administration, projects, or community topics creates avoidable gaps. Give every domain at least one deliberate review and reserve time to revisit the areas where your diagnostic evidence is weakest.
Do not confuse product familiarity with feature purpose
Knowing that GitHub has Actions, Copilot, Codespaces, Projects, and code scanning is not enough. Ask what each capability contributes, how it relates to repository work, and what it does not replace. Clear distinctions are more useful than a long list of product names copied from a course page.
Do not rely on stale localisation or unofficial summaries
The study guide warns that localised exam versions may not always be updated on the same schedule as English. It also says that available languages are listed on the Exam Details page. Check the official page close to scheduling, particularly if you plan to test in a language other than English, and use the current blueprint rather than an undated note.
Understand the evidenced exam-day and scheduling details
Microsoft states that the assessment takes 100 minutes, is proctored, and may include interactive components. The certification page directs candidates to schedule through Pearson VUE. Confirm the current appointment, delivery choices, policies, and any requirements in the official scheduling flow rather than relying on a general testing assumption.
Language and accommodation decisions
The certification page lists English, Spanish, Portuguese (Brazil), Korean, and Japanese as exam languages. If the exam is not available in your preferred language, the study guide says you can request an additional 30 minutes. Candidates who use assistive devices or need changes to the exam experience can request an accommodation through Microsoft’s credentials process.
Account ownership matters
Microsoft strongly recommends registering with a personal Microsoft account. The certification page warns that using an organisational work or school account can result in exam records being lost and unrecoverable if you leave that organisation. Make the account decision before scheduling, then confirm that your certification profile is connected to Microsoft Learn.
Test-centre and appointment research
Pearson VUE provides a test-centre locator that asks candidates to select the relevant exam programme and search by location. Use the official Pearson VUE route supplied by Microsoft, check the available appointment information for your location, and read the current instructions before committing. Do not infer availability, delivery format, or appointment timing from another certification programme.
Price and retake policy
Microsoft lists the GitHub Foundations exam price as US$99, with pricing based on the country or region where the exam is proctored. If you fail, Microsoft states that you may retake the certification exam 24 hours after the first attempt; later retake intervals vary under the retake policy. Verify the current price and policy during registration because these are scheduling details, not study assumptions.
Use the final week for retrieval, not content hoarding
In the final stage, stop collecting unrelated tutorials and work from your domain gap list. Review the official study guide, explain each domain without notes, complete the sandbox, and use the practice assessment to identify remaining uncertainty. A short, targeted review is more useful than beginning another broad course immediately before the appointment.
A final review checklist
Confirm that you can distinguish Git from GitHub; explain repositories, commits, branches, and pull requests; choose between issues and discussions; describe the role of Markdown; identify the purposes of Desktop and Mobile; explain the positions of Actions, code scanning, Copilot, Codespaces, and Projects; and discuss privacy, security, administration, and community participation in clear terms.
The day before scheduling or testing
Check the current exam page for language, price, appointment, and policy information. Confirm that your Microsoft Learn profile uses the intended personal Microsoft account and that any accommodation request has been handled through the official process. Complete the exam sandbox, then stop expanding the syllabus and preserve time for calm recall of the concepts you already studied.
What to do after the diagnostic review
Let your evidence determine the next action. If your explanations are clear and your practice-assessment review shows only isolated gaps, move toward scheduling. If you repeatedly confuse related features or cannot apply the workflow, return to the relevant Microsoft Learn module and practise before paying for an appointment. Readiness is a decision based on demonstrated understanding, not on a fixed number of study days.
A simple decision rule
Schedule when you can cover all seven domains, explain the central GitHub workflow, use the sandbox comfortably, and account for the gaps revealed by the official practice assessment. Delay when your preparation depends on memorised answers, when a whole domain remains untouched, or when you have not checked the current official scheduling information for your language and location.
Where to verify changes
Use the GitHub Foundations certification page for exam details, the GH-900 study guide for the measured skills and updates, Microsoft Learn training for structured preparation, and Pearson VUE for the relevant scheduling or test-centre process. These sources should remain your reference points when third-party pages disagree or when a product detail appears to have changed.
Conclusion
GitHub Foundations is best approached as a platform-understanding exam: learn the GitHub model, connect features to real collaboration decisions, and then validate each blueprint domain. Give Understand Git and GitHub basics its official priority without neglecting the remaining domains. Use Microsoft Learn’s study guide, learning resources, sandbox, and practice assessment, then confirm account, language, price, timing, and Pearson VUE arrangements through the current official pages before scheduling Exam GH-900.
Related exams
- GitHub-Actions exam — GitHub Actions Certificate Exam
- GitHub-Advanced-Security exam — GitHub Advanced Security GHAS Exam
- GitHub-Copilot exam — GitHub CopilotCertification Exam
