Free Practice Questions for the GitHub Certification GitHub-Foundations Exam (2026 Updated)

GitHub Flow is a simple, yet powerful, branching strategy that is widely used in modern software development. It emphasizes collaboration and flexibility.

GitHub Flow:

Option C is correct because GitHub Flow is a lightweight workflow designed for safe experimentation and collaboration. It involves creating branches for new features or fixes, opening pull requests for review, and merging changes back into the main branch after approval.

Incorrect Options:

Option A is incorrect because GitHub Flow uses a single main branch, not multiple primary branches.

Option B is incorrect because GitHub Flow is not specifically designed around releases; it is more focused on continuous development and integration.

Option D is incorrect because GitHub Flow is not strict or linear; it encourages branching and pull requests rather than direct changes on the main branch.

References:

GitHub Docs: Understanding the GitHub Flow

GitHub Guides: The GitHub Flow

=================

For private repositories on GitHub, the Wiki is accessible to anyone who has Read access to the repository. This means that if you can view the code and files in the repository, you can also view its Wiki. This makes Wikis a useful tool for documenting projects in a way that is available to all collaborators without requiring special permissions beyond those needed to access the repository itself.

=================

Creating a repository template in GitHub requires specific steps and permissions:

Creating a Repository Template:

Option A is correct because a user with Admin permissions can navigate to the repository's settings and enable the "Template Repository" option. This allows other users to generate new repositories from this template, which includes all branches, tags, and file history.

Other Options:

Option B is incorrect because "Maintain" permissions do not allow the creation of repository templates, and the option is not found in Organization settings but in the repository settings.

Option C is incorrect because the "Template Repository" option is in the repository settings, not in Organization settings.

Option D is incorrect because "Maintain" permissions do not grant the ability to create a repository template.

References:

GitHub Docs: Creating a Template Repository

=================

A distributed version control system (DVCS) like Git is best described as a system that ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata . This decentralized approach allows developers to work independently, with full access to the project's history and files, and later synchronize their changes with others. Unlike centralized systems, DVCS does not rely on a single central server, which provides greater flexibility and robustness in collaboration.

=================

GitHub Sponsors allows developers and organizations to financially support open-source contributors directly on the GitHub platform.

Setting Up a Sponsored Developer Profile:

Option D is correct because before a contributor can receive funding through GitHub Sponsors, they need

=================

The Codespaces lifecycle on GitHub includes several key steps:

Create : This is the step where a new Codespace is initiated.

Rebuild : A Codespace can be rebuilt to ensure that the environment is up-to-date with the latest code or configurations.

Delete : Once a Codespace is no longer needed, it can be deleted to free up resources.

Committing, cloning, or installing are typical Git operations but are not considered part of the specific lifecycle steps for a GitHub Codespace.

=================

In GitHub, labels are used to categorize issues and pull requests, and certain default labels are provided to help manage tasks:

Help Wanted Label:

Option C is correct. The "Help wanted" label is used to indicate that the maintainer of the repository needs assistance on a particular issue or pull request. This label helps in attracting contributors who might be interested in helping with specific tasks.

Other Options:

Option A ("Enhancement") is incorrect because it indicates a request for a new feature or improvement rather than a call for help.

Option B ("Question") is incorrect because it is used to flag issues or pull requests that seek clarification or additional information, not necessarily requiring assistance.

Option D ("Documentation") is incorrect because it labels issues or PRs related to documentation, not for seeking help.

References:

GitHub Docs: Using Labels

=================

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.

=================

The primary benefits of using GitHub issues templates include:

A. To automatically label or assign newly created issues : Issue templates can be configured to automatically apply labels or assign users when the issue is created, helping to streamline triage and management processes.

B. To provide an easy-to-fill-out form for creating new issues : Templates provide a standardized format for submitting issues, ensuring that all necessary information is captured and reducing the need for follow-up questions.

Coercing existing issues into a standard format or automatically creating new branches when issues are created are not functions provided by GitHub issues templates.

=================

After 30 minutes of inactivity, a GitHub Codespace will time out . This is designed to conserve resources when the Codespace is not being actively used. The session will be paused, and you'll need to reconnect to resume your work. However, the Codespace is not deleted, and any unsaved changes might not be lost but should be committed or saved to prevent data loss.

=================

In GitHub Discussions, several default categories are provided to help organize conversations within a project. One of the default categories is Show and tell . This category is designed for users to showcase their work, share progress, or discuss achievements with the community. The other options listed (Bug report, Daily check-in, Security concern) are not default categories but could be custom categories created by the repository maintainers.

=================

GitHub Sponsors is a program designed to provide a platform for developers and companies to financially support open-source projects and their maintainers.

Financial Support for Open Source Projects:

Option D is correct because the main purpose of GitHub Sponsors is to allow members of the developer community, including individuals and organizations, to financially support open-source projects and maintainers. This helps sustain open-source development by providing developers with the resources they need to continue their work.

Incorrect Options:

Option A is incorrect because GitHub Sponsors is not based on project popularity (e.g., stars); it is based on voluntary contributions.

Option B is incorrect because while GitHub provides the platform, the purpose of GitHub Sponsors is not for GitHub itself to fund projects, but to enable the broader community to do so.

Option C is incorrect because GitHub Sponsors is not a marketplace for purchasing software but a platform for supporting developers.

References:

GitHub Docs: GitHub Sponsors

=================

In GitHub, when viewing the list of projects for an organization, a user can identify a GitHub Projects template by selecting the Templates tab . This tab specifically lists available templates that can be used to create new projects based on predefined structures and workflows.

=================

A user's GitHub profile typically includes public information such as a personal biography, profile picture, and a list of public repositories. More sensitive information, like email addresses and passwords, is not publicly displayed.

Personal Biography and Profile Picture:

Option A is correct because these are standard elements displayed on a user's public GitHub profile. This information is meant to provide a brief introduction to the user and their interests or skills.

Incorrect Options:

Option B is incorrect because public SSH keys may be associated with a user's account but are not displayed by default on the profile page.

Option C is incorrect because private repositories are not listed on a public profile.

Option D is incorrect because a user's email address and password are private information and not displayed on their public profile.

References:

GitHub Docs: Managing Your Profile

=================

GitHub provides repository admins with a feature called "Insights" where they can view various pre-built visualizations and analytics related to the repository.

Insights:

Option C is correct because the "Insights" tab in a GitHub repository offers various pre-built visualizations, including contributions, traffic, code frequency, dependency graphs, and more. This helps admins and maintainers track the project's activity and health.

Other Options:

Option A (Settings) is incorrect because the Settings tab is where you configure repository settings, permissions, and integrations, but it does not provide visualizations of repository data.

Option B (Issues) is incorrect because the Issues tab is used for tracking bugs, enhancements, and other tasks but does not provide data visualizations.

Option D (Charts) is incorrect as there is no "Charts" tab or section in GitHub. The correct location for data visualizations is under "Insights."

References:

GitHub Docs: Viewing Repository Insights

=================

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 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.

=================

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.

=================

Organization owners on GitHub have control over how GitHub Actions can be used within their organization. They can enforce restrictions to ensure security and compliance with organizational policies.

Allow Actions That Use Self-Hosted Runners:

Option A is correct because organization owners can configure the usage of self-hosted runners, allowing greater control over the environment where actions are run.

Allow Specified Actions:

Option C is correct because organization owners can allow only specific actions to run, adding a layer of security by limiting actions to those that have been vetted.

Allow Actions by Marketplace Verified Creators:

Option D is correct because organization owners can choose to allow actions created by GitHub Marketplace verified creators, ensuring that only trusted actions are used.

Incorrect Options:

Option B is incorrect because GitHub Actions are not designed to be run directly from a Codespace; Codespaces are for development environments.

Option E is a valid choice, but since the prompt asks for only three answers, it is not included in this response.

References:

GitHub Docs: Managing GitHub Actions Settings for Your Organization

=================