GH-900 Practice questions
GitHub Foundations
0/5 checked
- free questions
- 5
- with answers
- in the full set
- 144
- question types
- 2
Updated
-
Question 1
Single answer
How are commits related to pull requests?
Show answer
Correct answer
-
A
Commits are made on a branch that can have a linked pull request.
Explanation
Commits and pull requests (PRs) are fundamental concepts in Git and GitHub workflows, particularly in collaborative software development.
Commits:
Commits are individual changes or updates made to the codebase. Each commit is identified by a unique SHA-1 hash and typically includes a commit message describing the changes.
Commits are made to a specific branch in the repository. The branch could be the main branch, or more commonly, a feature branch created for specific work or a feature.
Pull Requests (PRs):
A pull request is a mechanism for developers to notify team members that a branch is ready to be merged into another branch, usually the main branch.
PRs are used to review code, discuss changes, and make improvements before the branch is merged into the target branch.
Relationship Between Commits and PRs:
Option A is correct because commits are made on a branch, and this branch can have a pull request associated with it. The pull request tracks the branch’s commits and allows for code review before merging into the target branch.
Commits can be added to the branch both before and after the pull request is created. Any new commits pushed to the branch are automatically included in the pull request.
Incorrect Options:
Option B is incorrect because commits can be made both before and after a pull request is created.
Option C is incorrect because it suggests that commits can only be made before a pull request is created, which is not true.
Option D is incorrect because commits are not made on a pull request; they are made on a branch. The pull request links a branch to another branch (e.g., feature branch to the main branch).
GitHub Documentation: About Pull Requests
GitHub Docs: Understanding the GitHub Flow
Git Documentation: Git Basics - Getting a Git Repository
=================
No comments yet. Start the discussion.
-
A
-
Question 2
Multiple answer
Who can be assigned to an Issue or pull request?
(Each answer presents a complete solution. Choose two.)
Show answer
Correct answer
-
B
Anyone who has commented on the Issue or pull request
-
D
Anyone with write permissions to the repository
Explanation
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 Docs: Assigning Issues and Pull Requests
GitHub Docs: Permission Levels for a Repository
This detailed explanation provides clarity on GitHub's assignment mechanics for issues and pull requests, reflecting the platform's collaborative nature.
=================
No comments yet. Start the discussion.
-
B
-
Question 3
Single answer
Which of the following is an Innersource development practice?
Show answer
Correct answer
-
B
Sharing code between teams within the organization
Explanation
Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across different teams within the organization.
Sharing Code Between Teams:
Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality, and allows for reuse of code, reducing duplication of efforts.
Incorrect Options:
Option A is incorrect because adopting open-source code into the organization is related to using open-source software, not specifically to innersource practices.
Option C is incorrect because removing open-source code from the organization is contrary to the principles of both open source and innersource.
Option D is incorrect because making all repositories publicly accessible refers to open source, not innersource. Innersource typically involves keeping code internal to the organization.
GitHub Docs: What is Innersource?
Innersource Commons: The Basics
=================
No comments yet. Start the discussion.
-
B
-
Question 4
Single answer
Which of the following GitHub syntax formats is consistent with the associated text?
Show answer
Correct answer
-
C
<!-- This is a comment -->
Explanation
GitHub supports various syntax formats that align with Markdown and HTML conventions. Here's a breakdown of the provided options:
Comment Syntax:
Option C is correct. The syntax <!-- This is a comment --> is used in Markdown files to insert comments. These comments will not be rendered in the final output, making them useful for adding notes or instructions within the code or documentation.
Incorrect Options:
Option A (* This is a heading) is incorrect because an asterisk (*) denotes an unordered list item, not a heading. A heading in Markdown is typically created with one or more hash symbols (#).
Option B (This is a link) is incorrect because this is plain text and not the syntax for creating a link. The correct syntax would be [This is a link](URL).
Option D (This is bolded text) is incorrect because this is plain text, not the correct Markdown syntax for bold text, which should be This is bolded text or __This is bolded text__.
Option E (1. This is an ordered list) is incorrect as it does represent an ordered list item, but it was not the syntax format asked about in the question. The question specifically focuses on matching associated text with syntax, where only the comment option is correct.
GitHub Flavored Markdown (GFM)
GitHub Docs: Basic writing and formatting syntax
=================
No comments yet. Start the discussion.
-
C
-
Question 5
Multiple answer
What are the key areas of focus for GitHub?
(Each answer presents a complete solution. Choose three.)
Show answer
Correct answer
-
A
Nurturing a community that supports open source principles
-
B
Providing access and opportunities for developers
-
D
Building a technology platform for secure code sharing and collaboration
Explanation
GitHub focuses on several key areas that align with its mission to support developers and foster collaboration:
Nurturing a Community That Supports Open Source Principles:
Option A is correct. GitHub is a major advocate for open-source software development, providing tools and platforms that enable open collaboration. GitHub hosts millions of open-source projects and supports a community-driven approach to software development.
Providing Access and Opportunities for Developers:
Option B is correct. GitHub provides a wide range of resources, such as GitHub Education, GitHub Actions, and GitHub Marketplace, to empower developers. These tools and opportunities help developers of all levels to learn, contribute, and improve their skills.
Building a Technology Platform for Secure Code Sharing and Collaboration:
Option D is correct. GitHub’s core function is to provide a platform where developers can securely share code and collaborate. Features like private repositories, branch protections, and GitHub Actions for CI/CD (Continuous Integration/Continuous Deployment) workflows highlight this focus.
Incorrect Options:
Option C is incorrect because GitHub is not a social media platform for project managers; it is a code hosting platform with social features primarily aimed at developers.
Option E is incorrect because GitHub does not focus on hosting video calls. While some integrations might allow for video conferencing, it is not a core focus of GitHub.
GitHub Docs: The GitHub Developer Experience
GitHub Docs: About GitHub
This detailed explanation covers the primary focuses of GitHub, emphasizing its role in the open-source community and its commitment to providing a secure and collaborative platform for developers.
=================
No comments yet. Start the discussion.
-
A
- Unlock to see this question
- Unlock to see this question
139 questions locked
Unlock all 144 GH-900 questions
You’ve had 5 for free. The other 139 work just like them: pick an answer, then check it.
- Questions
- 144, each with its answer
- Explanations
- 66% of questions explained
- Formats
- Single answer, Multiple answer
- Version
- 8.2
- Access
- 3 months from purchase
One-time payment
$49.00
Secure checkout