GH-900 GitHub Foundations Questions and Answers

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.

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.

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

The CODEOWNERS file in a GitHub repository is used to define individuals or teams that are responsible for specific parts of the codebase. When changes are made to files or directories that match the patterns specified in the CODEOWNERS file, GitHub automatically requests reviews from the listed code owners.

Setting Reviewers Automatically:

Option D is correct because the primary purpose of a CODEOWNERS file is to automatically set reviewers for pull requests that affect the specified files or directories. This ensures that the appropriate team members are notified and review the changes before they are merged.

Incorrect Options:

Option A is incorrect because the CODEOWNERS file does not restrict who can edit specific files; it only influences who is required to review changes.

Option B is partially related but not fully accurate because while CODEOWNERS does require certain reviews, it does not mandate peer review for all code changes.

Option C is incorrect because the CODEOWNERS file does not define access permissions for the repository; it deals with code review processes.

GitHub Copilot for Business offers several features that are tailored to the needs of organizations, providing more control, security, and support compared to the individual version.

Organization-wide Policy Management:

Option B is correct because Copilot for Business allows organizations to manage policies across their entire user base, providing control over how Copilot is used within the organization.

Blocking Suggestions Matching Public Code:

Option C is correct because Copilot for Business includes enhanced security features, such as blocking code suggestions that match public code to prevent inadvertent use of unlicensed code.

Support for Organization or Enterprise GitHub Accounts:

Option E is correct because Copilot for Business supports integration with GitHub Enterprise accounts, offering additional administrative controls and integration capabilities.

Incorrect Options:

Option A (multi-line function suggestions) is a feature available in both individual and business versions, so it does not differentiate the business offering.

Option D (VPN proxy support via self-signed certificates) is not a primary differentiator of Copilot for Business.

Option F (plugs directly into the editor) is true for both individual and business versions, so it is not unique to Copilot for Business.

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.

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

To locate an existing GitHub Action provided by a GitHub-approved vendor, you can use the following methods:

Verification Badge:

Option C is correct because actions provided by GitHub-approved vendors will typically have a verification badge. This badge indicates that the action is from a trusted source, giving users confidence in its security and reliability.

Search the GitHub Marketplace:

Option F is correct because GitHub Marketplace is the official location to find and install actions, including those provided by third-party vendors. You can search for actions by the vendor ' s name to find the specific one you need.

Incorrect Options:

Option A is not necessary to locate an existing action; creating a workflow file is for implementing the action, not locating it.

Option B is incorrect because searching the vendor’s website for a github.yaml index is not a standard practice for finding actions.

Option D is incorrect because installing a GitHub App is unrelated to finding an existing action.

Option E is incorrect because adding a vendor as an allowed Actions Source is a configuration step for using the action, not for locating it.

The primary purpose of creating a security policy in a GitHub repository is to guide users and contributors on how to report security vulnerabilities in a responsible and secure manner. This policy outlines the preferred method of communication, timelines, and any other pertinent information related to handling security issues.

Security Policy:

Option C is correct because a security policy provides guidelines for responsibly disclosing security vulnerabilities. This helps maintainers respond to and address security concerns promptly and securely, thereby protecting the project and its users.

Incorrect Options:

Option A is incorrect because ensuring peer code review is a best practice for code quality, but it is not the primary purpose of a security policy.

Option B is incorrect because push protection for secrets is managed through repository settings, not the security policy.

Option D is incorrect because customizing Dependabot configuration is related to dependency management, not directly to security policies.

GitHub provides several pre-defined repository roles that determine the level of access and permissions a user has within a repository. The roles that are included by default are:

Triage : Allows users to manage issues and pull requests without write access to the code.

Maintain : Provides more extensive access, including managing settings, but without full administrative control.

Write : Grants permission to push changes and manage issues and pull requests.

Roles like " Security " and " Delete " are not standard pre-defined roles, and " View " is generally referred to as " Read " in GitHub ' s permission structure.

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

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.

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

Secret gists on GitHub are " unlisted " gists, meaning they are not publicly discoverable but can be viewed by anyone who has the URL.

Visibility of Secret Gists:

Option A is correct because secret gists can be viewed by anyone who has the direct URL, making them accessible yet unlisted.

Incorrect Options:

Option B is incorrect because secret gists do not require GitHub Enterprise; they are available on all GitHub accounts.

Option C is incorrect because secret gists do not appear on the gist Discover page.

Option D is incorrect because secret gists do not have an " assigned access " feature; access is determined by sharing the URL.

GitHub Mobile provides a streamlined experience for managing your GitHub notifications and participating in discussions, but it does not offer full functionality compared to the desktop or web interface.

Managing Notifications:

Option E is correct because GitHub Mobile allows users to manage notifications, keeping them up to date with their repositories, issues, pull requests, and other activities on GitHub.

Incorrect Options:

Option A is incorrect because GitHub Mobile cannot be used as a self-hosted runner.

Option B is incorrect because managing enterprise and organization settings is not supported in GitHub Mobile.

Option C is incorrect because GitHub Mobile does not offer a chat or voice calling feature.

Option D is incorrect because forking and cloning repositories are not actions available in GitHub Mobile.

The qualifier mentions: is used in GitHub ' s search functionality to find issues that mention a certain user. For example, if you want to find all issues where a specific user is mentioned, you would use mentions:username . This helps in tracking where a user has been involved in discussions across issues or pull requests.

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

GitHub provides a powerful search syntax to filter and find specific issues across repositories in an organization.

Search Query Syntax:

Option A is correct because the query org:Avocado is:issue label:guacamole " 404 error " is the best way to search for all issues within the " Avocado " organization that contain the text " 404 error " and are labeled with " guacamole " . This query is precise and leverages GitHub’s advanced search capabilities.

Incorrect Options:

Option B is incorrect because it requires manual filtering in a specific repository rather than searching across the entire organization.

Option C is incorrect because selecting " Issues " in the filter by section is redundant when using the query is:issue .

Option D is incorrect because accessing organization settings to look for repository labels is not relevant to searching for issues.

GitHub Desktop is a graphical interface that allows users to interact with GitHub repositories. It simplifies certain Git operations without the need for command-line usage.

GitHub Desktop Capabilities:

Option C is correct because GitHub Desktop allows users to add local repositories to their GitHub account, clone repositories from GitHub to their local machine, and manage repositories effectively.

Incorrect Options:

Option A is incorrect because GitHub Desktop does not support creating or managing issues directly; this is done through the GitHub web interface.

Option B is incorrect because reviewing and approving pull requests is also managed through the GitHub web interface.

Option D is incorrect because commenting on discussions is done on the GitHub platform, not through GitHub Desktop.

Option E is incorrect because GitHub Desktop does not integrate with office suite software.

When multiple README files exist in different locations within a GitHub repository, the README.md file located in the root directory of the repository will be displayed first by default. This file serves as the main documentation for the repository and is automatically rendered on the repository ' s home page.

Root Directory:

Option C is correct because the README.md file in the root directory is prioritized and displayed first on GitHub. This is the standard behavior for how GitHub presents documentation.

Incorrect Options:

Option A ( .github ) is incorrect because while a README.md file in the .github directory might be used for certain configurations, it is not the first to be displayed.

Option B ( /src ) is incorrect because the README.md in the src directory is not prioritized over the root.

Option D ( /docs ) is incorrect because documentation in the /docs folder is typically secondary to the root README.md .

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.

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

In GitHub, issues and pull requests (PRs) are essential tools for managing work and collaboration in a project. Assigning individuals to these issues or PRs is a way to indicate responsibility for addressing the issue or completing the PR.

Anyone with write permissions to the repository:

Users who have write permissions to a repository can be assigned to issues and pull requests. Write permissions allow users to push changes to the repository, create branches, and modify issues and pull requests. Assigning them to an issue or PR ensures they are recognized as responsible for the task.

Anyone who has commented on the Issue or pull request:

GitHub allows you to assign issues or pull requests to users who have already engaged with the discussion by commenting on it. This feature is particularly useful for quickly assigning tasks to those who are already involved in the conversation.

Incorrect Options:

Option A is incorrect because having an enterprise GitHub account alone does not necessarily grant the ability to be assigned to issues or PRs. Permission to assign is based on repository-specific roles and permissions.

Option C is incorrect because not all personal GitHub accounts can be assigned to issues or PRs. The user needs either write permissions to the repository or must have commented on the issue or PR.

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.

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

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.

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

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.

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