Free GitHub-Foundations Practice Test Questions and Answers (2026)

As a GitHub user, you can configure two-factor authentication (2FA) to secure your account by

navigating to Settings -> Password and Authentication -> 2FA. This section in the GitHub user

interface allows you to set up and manage your 2FA methods, which provide an additional layer of

security beyond just your password.

On GitHub, certain actions automatically subscribe you to conversations so that you receive

notifications about further activity in that thread.

Opening a Pull Request or Issue:

Option C is correct because when you open a pull request or issue, you are automatically subscribed

to the conversation and will receive notifications for any updates.

Commenting on a Thread:

Option D is correct because commenting on an issue or pull request automatically subscribes you to

that thread, ensuring you are notified of further comments or changes.

Being Assigned to an Issue or Pull Request:

Option E is correct because when you are assigned to an issue or pull request, you are automatically

subscribed to notifications related to it.

Incorrect Options:

Option A is incorrect because pushing a commit to the default branch does not automatically

subscribe you to conversations.

Option B is incorrect because being added as a repo admin does not automatically subscribe you to

specific conversations unless you engage with them.

Reference:

GitHub Docs: Subscribing to Notifications

It is recommended to deploy from your feature branch before merging into the main branch to

ensure the changes are verified and validated in a production environment. This practice helps in

identifying any potential issues or bugs in a real-world scenario before the changes are permanently

integrated into the main branch. By deploying from the feature branch, developers can catch and

address issues early, reducing the risk of introducing bugs into the main branch, which is usually

considered the stable branch.

In GitHub Flow, creating a new branch is a key step in the development process that allows for

isolated development of new features or fixes without affecting the main codebase.

Experimenting with New Features or Fixes:

Option C is correct. The primary purpose of creating a new branch in the GitHub flow is to provide a

safe space to experiment with new features or fixes. This allows developers to work on changes

independently and only merge them into the main branch after they have been reviewed and

approved.

Incorrect Options:

Option A (To create a backup of the main branch) is incorrect because branches are not typically used

for backups; they are for active development.

Option B (To capture information about an issue) is incorrect because issues are tracked separately;

branches are for code changes.

Option D (To incorporate changes from a review) is incorrect because incorporating changes is done

during the pull request process, not when creating a branch.

Reference:

GitHub Docs: GitHub Flow

From a discussion post on GitHub, a user can Create an issue from the discussion. This feature allows

users to turn a discussion into an actionable item by creating an issue directly from the discussion

thread. This is particularly useful when a conversation identifies a bug, task, or enhancement that

needs to be tracked in the repository.

GitHub Desktop is a standalone application that provides a graphical user interface (GUI) for

interacting with GitHub repositories, as opposed to the command-line or web-based interfaces

available on github.com.

Graphical User Interface:

Option D is correct because GitHub Desktop offers a GUI, making it easier for users to manage

repositories, perform commits, and handle other Git-related tasks without needing to use the

command line.

Incorrect Options:

Option A is partially correct in that GitHub Desktop is a standalone application, but the key difference

is the GUI.

Option B is incorrect because GitHub Desktop does not specifically enable integration with office

suite applications.

Option C is incorrect because GitHub Desktop is available on both Windows and macOS.

Option E is incorrect because GitHub Desktop is not a self-hosted version of GitHub; it is a client

application for accessing GitHub repositories.

Reference:

GitHub Docs: GitHub Desktop Documentation

GitHub Projects is a newer, more powerful version of project management within GitHub, offering

enhanced features over the classic version.

Multiple Layout Views:

Option A is correct because GitHub Projects supports multiple views, such as board, table, and

timeline views, allowing users to visualize their work in different ways according to their needs.

Insights:

Option B is correct because GitHub Projects provides insights and analytics, enabling teams to track

progress and make data-driven decisions.

Incorrect Options:

Option C is incorrect because while GitHub Copilot is a tool for code suggestions, it is not directly

integrated with GitHub Projects as a feature.

Option D is incorrect because both GitHub Projects and GitHub Projects Classic can be connected to

third-party tools, so it is not an exclusive advantage of the newer GitHub Projects.

Reference:

GitHub Docs: Managing Projects

To highlight a post at the top of the Discussions page on GitHub, you can Pin the discussion. Pinning a

discussion ensures it remains prominently visible at the top of the list, making it easier for others to

find and participate in that discussion. This is particularly useful for important announcements or

frequently referenced topics.

GitHub is a cloud-based platform that provides hosting for software development and version control

using Git. It offers tools for collaboration, project management, and security to create a safe and

productive environment for developers.

GitHub Overview:

Option B is correct because GitHub is primarily known as a cloud-based hosting service for Git

repositories, offering a collaborative environment where developers can work together on projects,

manage version control, and implement security practices.

Incorrect Options:

Option A is incorrect because GitHub is not proprietary in the sense of being closed off from version

control standards; it is widely recognized as an open platform for collaboration.

Option C is incorrect because, while GitHub is accessible to new developers, it is designed for

developers of all skill levels and not specifically tailored for beginners.

Option D is incorrect because GitHub is not a centralized version control system; it supports Git,

which is distributed.

Reference:

GitHub Docs: About GitHub

A GitHub repository serves as a collaborative space where developers can share and manage code

files, track changes, and store revision history. It is much more than just a folder or simple tool; it is a

comprehensive version control system that allows teams to collaborate effectively on codebases.

Repositories enable developers to work together, manage contributions, review code, and maintain

a complete history of every change made to the project.

Pull requests (PRs) on GitHub can have several statuses that indicate their current state in the

development and review process:

Draft:

Option A is correct. A pull request can be in a "Draft" status, indicating that it is a work in progress

and not yet ready for review.

Closed:

Option B is correct. A pull request can be "Closed" without being merged, which might happen if the

proposed changes are not needed or are incorporated differently.

Merged:

Option D is correct. A pull request that has been reviewed and approved can be "Merged" into the

target branch, indicating that the changes have been successfully incorporated.

Open:

Option F is correct. An "Open" pull request is one that is active and awaiting review or further action.

Incorrect Options:

Option C (Rebasing) is incorrect because "Rebasing" is not a status; it's an operation that can be

performed on branches.

Option E (Modified) is incorrect because there is no "Modified" status for pull requests.

Reference:

GitHub Docs: About Pull Requests

GitHub Projects is a flexible and powerful tool for project management that allows users to manage

their work with ease. One of the key characteristics of GitHub Projects is the ability to create and

customize multiple views. This feature enables teams to tailor the project management experience

to their specific workflow needs, offering various ways to visualize tasks, issues, and work items.

Custom Views: You can set up different views like Kanban boards, tables, or timelines, and apply

filters to show only what is relevant for a particular aspect of the project. This customization allows

teams to organize their work in a way that best suits their processes, making it a highly adaptable

project management tool.

Other options, such as visualizing commit history (which would fall under the 'Insights' feature),

importing Gantt charts (which GitHub Projects does not natively support), or enforcing required

fields (which might relate to form-based tools but not to GitHub Projects specifically), do not align

with the key characteristics of GitHub Projects.

In GitHub, an organization member is a user who has been added to an organization and is subject to

the organization's base permissions and policies. An outside collaborator is a user who is not a

member of the organization but has been granted access to one or more repositories within the

organization.

Here’s the difference between an organization member and an outside collaborator:

Organization Members:

Members are subject to the organization's base permissions, which apply across all repositories

within the organization. These permissions might include read, write, or admin access, depending on

what has been set as the default.

Members consume paid licenses if the organization is on a paid plan.

Members are required to have two-factor authentication (2FA) if the organization enforces it.

Outside Collaborators:

Outside collaborators do not have organization-wide permissions. They only have access to specific

repositories to which they have been granted permission. This means organization base permissions

do not apply to them (making option A correct).

Outside collaborators do not consume paid licenses. They are only counted toward the license if they

are made organization members.

Outside collaborators can be granted any level of permission, including the admin role on specific

repositories.

Two-factor authentication (2FA) can be enforced for outside collaborators at the repository level,

depending on the organization's security settings.

Given this information, option A is the correct answer: "Organization base permissions do not apply

to outside collaborators."

Reference:

GitHub Documentation: Roles in an organization

GitHub Documentation: About outside collaborators

GitHub Documentation: Managing repository access for your organization

Two recommended ways to improve the discoverability of a repository on GitHub are:

B . Create a README file describing the repository: A well-written README file provides essential

information about the project, such as what it does, how to use it, and how to contribute. This is

often the first thing potential users or contributors will see, making it critical for discoverability.

D . Add topics to classify the repository: Adding topics to your repository helps classify it under

specific categories, making it easier for others to find it through GitHub’s search and exploration

features. Topics act like tags, helping to connect your project with users interested in similar subjects.

Registering a repository with GitHub search and adding labels are not applicable actions for

improving discoverability in the broader sense.

GitHub Pages is a feature provided by GitHub that allows you to create webpages hosted and

published through GitHub repositories. It is commonly used for hosting project documentation,

personal websites, or blogs directly from a GitHub repository. It integrates seamlessly with the

repository, making it easy to deploy and manage website content.