Description

For learners studying for GitHub Foundations
What you'll learn
Practice pack content
Domain 1 - Understand Git and GitHub basics
Domain 2 – Work with GitHub repositories
Domain 3 – Collaborate using GitHub
Domain 4 – Apply modern development practices
Domain 5 – Manage projects with GitHub
Domain 6 – Understand privacy, security, and administration
Domain 7 – Explore the GitHub community
Final Exam Simulators
Exam Study Guide
Interactive Flashcards
Try 3 GitHub Foundations GH-900 practice questions
Choose an answer, explore the explanation, and see why the other options are less suitable. Three short scenarios. No sign-in required.
Work with GitHub repositoriesTopic · Repository management
1. A clear guide for new contributors
New contributors to a GitHub repository keep opening pull requests without following the team's testing and formatting expectations. The maintainer wants one standard file explaining how to submit changes, which checks to run, and what information to include. Which file should contain this guidance?
- Update README.md with the project overview and basic setup instructions.
- Update CONTRIBUTING.md with the required workflow and submission guidance.
- Update CODEOWNERS with the people responsible for reviewing changed files.
- Update SECURITY.md with the process for reporting security vulnerabilities.
Answer and full explanation
Correct answer: B — CONTRIBUTING.md provides the contribution guidelines.
Why B is correct
A CONTRIBUTING.md file explains how people should contribute to a project. Testing steps, formatting expectations and submission instructions all belong in those contribution guidelines. Keeping the requirements together gives new contributors a reference before opening a pull request. GitHub can surface a link to the guidelines when contributors create issues or pull requests. The other files have useful roles, but they do not specifically serve as the project's contribution guide.
Why the other options are less suitable
- A — README.md: A README introduces the project and commonly explains what it does and how to get started. It can link to contribution guidance, but CONTRIBUTING.md is the dedicated file for the requested submission rules.
- C — CODEOWNERS: CODEOWNERS identifies people or teams responsible for particular files and supports review requests. It does not document the testing steps or submission instructions that contributors should follow.
- D — SECURITY.md: SECURITY.md explains supported versions and how to report security vulnerabilities. That guidance is useful for security reports, not the general contribution workflow described here.
Key takeaway: Use CONTRIBUTING.md for contribution instructions; distinguish it from project introductions, code ownership and security reporting.
Read two more sample questions
Collaborate using GitHubTopic · Collaboration tools
2. Close the issue when the fix is merged
A maintainer has opened a pull request targeting the default branch, main, to fix issue #42 in the same repository. The issue should remain open during review and close automatically when the pull request is merged. Which action creates the required closing relationship?
- Add "Closes #42" to a comment on the pull request.
- Assign the same milestone to the issue and pull request.
- Add "Related to #42" to the pull request description.
- Add "Closes #42" to the pull request description.
Answer and full explanation
Correct answer: D — Use the closing keyword in the pull request description.
Why D is correct
GitHub recognizes supported closing keywords in a pull request's description. Closes #42 identifies the issue in the same repository and creates the closing relationship. Because the pull request targets the default branch, GitHub applies this relationship when it is merged. Merely opening the pull request does not close the issue. This preserves the issue during review and closes it when the fix reaches main.
Why the other options are less suitable
- A — Keyword in a comment: A comment can reference the issue and provide context for reviewers. The closing-keyword mechanism requires the pull request description or a qualifying commit message, not an ordinary comment.
- B — A shared milestone: Milestones group issues and pull requests for progress tracking. Sharing a milestone does not establish that merging one particular pull request should close the issue.
- C — A descriptive reference: The issue number provides a reference that readers can follow. Related to is not a supported closing keyword, so this wording does not trigger automatic closure.
Key takeaway: For automatic issue closure, use a supported closing keyword in a pull request targeting the default branch.
Apply modern development practicesTopic · Automation and AI tools
3. A development environment in the browser
A learner needs to edit a repository, install dependencies, and run tests from an interactive terminal. They must work entirely in a browser without installing development tools on their computer, and their account can use Codespaces. Which GitHub option best meets these requirements?
- Open the repository in a browser-based GitHub Codespaces environment.
- Open the repository in the lightweight github.dev browser editor.
- Run a GitHub Actions workflow that executes the repository's tests.
- Clone the repository locally using the GitHub Desktop application.
Answer and full explanation
Correct answer: A — GitHub Codespaces supplies a cloud development environment.
Why A is correct
GitHub Codespaces provides a development environment hosted in the cloud. The learner can connect through a browser and work with repository files. Unlike the lightweight github.dev editor, a codespace supplies compute resources and an integrated terminal. Dependencies and tests can run in that remote environment rather than on the local computer. This meets the requirement for interactive development without installing local development tools.
Why the other options are less suitable
- B — The github.dev editor: The github.dev editor is useful for browsing files, making edits and committing changes in a browser. It does not provide the compute or integrated terminal needed to install dependencies and run tests.
- C — A GitHub Actions workflow: GitHub Actions can automate test execution on a runner. That serves an automated workflow, not the interactive browser-based development environment requested here.
- D — GitHub Desktop: GitHub Desktop provides a graphical application for working with repositories on a local computer. It does not supply a browser-only cloud environment and would require local software.
Key takeaway: Choose Codespaces for browser-accessible development with compute and a terminal; github.dev is a lightweight editor.
Preview complete
You have tried all three samples
Review the explanations or try the samples again. This short preview covers only a small part of the exam objectives.
Your sample score resets when this page reloads.
Your practice pack includes
More ways to make each study session count
Focus on a topic, practise under a time limit, or return to the supporting resources before your next attempt.
Domain-based practice
Timed practice sets
Study guide
Flashcards
Requirements
- Basic experience with Git, repositories, branches and pull requests will help. The official guide recommends practical GitHub familiarity; its audience includes both developers and non-developers.
- Combine questions with foundational study and exercises in a repository you own or may use. Practise commits, pull requests and issue tracking; no bundled lab environment is assumed.
- You will need an internet-connected device, a current web browser and an ExamsDigest account to access this online practice product and review your study work.
Know the exam you’re studying for
These details describe GitHub’s official GitHub Foundations GH-900 exam.
What our students say
“I had used GitHub for small projects, but studying for GH-900 showed me how much I had overlooked. The practice questions helped me identify gaps around pull requests, repository files and collaboration, so I knew what to revisit.”
Alex Harrison
✓ Verified Review
“The explanations helped even when I chose the correct answer. Reading why the other options didn’t fit made it easier to tell whether I understood the topic or had just guessed.”
Emily Dawson
✓ Verified Review
“I used ExamsDigest alongside the GitHub documentation and a repository of my own. After working through the questions, I tried the workflows myself. Linking issues to pull requests and comparing Codespaces with the browser editor finally started to make sense.”
Samuel Bennett
✓ Verified Review
Your questions, answered.
Which GitHub Foundations exam does this practice target?
This practice targets GitHub Foundations, exam GH-900, using the skills outline identified as January 2026 in the official study guide. Before purchasing, compare the listed product topics and resources with the objectives for your planned exam. GitHub Foundations is different from the GitHub Actions, Administration and Copilot certifications, so check the certification name as well as the code.
Do I need to be a developer?
No. The official audience includes both developers and non-developers who use GitHub. Familiarity with repositories, commits, branches, pull requests and basic project collaboration will help you understand the scenarios. This is a foundational exam rather than an advanced programming assessment. New users should build practical familiarity with those features alongside questions instead of relying only on definitions or memorized answers.
How should I combine questions with GitHub practice?
Use a repository you own or are authorized to work in alongside your study. Try editing a README, committing a change on a branch, opening a pull request and linking it to an issue. Then explain why each step belongs in the workflow. These suggested exercises complement question practice; they do not imply that this pack includes hosted labs, Codespaces usage or paid GitHub tools.
How should I use incorrect answers?
Use each mistake to identify a distinction you have not yet understood, such as a repository file’s purpose or the difference between editing code and running it. Compare the explanation with your reasoning, revisit the relevant documentation, and try a different scenario. Focus on explaining your choice rather than remembering its letter; repeated-question scores do not guarantee an official exam result.
Does the preview match the official exam format?
No. These three examples each have four choices and one correct answer. The official exam is proctored and may include interactive components, so the preview is not a reproduction of the full exam. Use the vendor-linked exam sandbox to become familiar with official navigation, and check the product description separately for its included practice formats.
Does completing this practice earn the certification?
No. Completing practice questions does not award GitHub Foundations. Earning the credential requires passing the official GH-900 exam and meeting the applicable candidate requirements and agreements. Use the official certification page for booking, and review the product terms for any voucher arrangements. Do not assume that buying practice questions also books your exam or includes an exam voucher.
30-day conditional refund policy
Eligible requests must be made within 30 calendar days, with no more than 20% of any included simulator completed. The purchase must not already be refunded or under a payment dispute or chargeback. Other provisions apply; mandatory consumer rights remain unaffected.
Useful links for your preparation



