GH-900 Practice Questions

Forking a repository on GitHub is a common practice, especially when contributing to open-source projects or when you want to build on existing work. Here are the two main reasons for forking a repository:

B.  

To propose changes to the base repository :

One of the primary reasons for forking a repository is to make changes or improvements that you can later propose to the original repository (often called the " upstream " repository). This is typically done through a pull request. By forking the repository, you get your own copy of the project where you can freely experiment, make changes, and then propose those changes back to the original project.

C.  

To create a new repository based on an existing one :

Forking is also used to create a new repository that is a copy of an existing one. This allows you to work on the project independently of the original repository, effectively creating a new direction for the project or using it as a starting point for a different purpose. This is particularly useful for customization, experimentation, or when you want to build something different while still leveraging the existing codebase.

Explanation of Other Options :

A.  

To create an issue or open a discussion :

This is incorrect because creating an issue or opening a discussion can be done directly on the original repository without needing to fork it. Forking is unnecessary for these actions.

D.  

To create a new branch to develop a new feature :

While creating a new branch is related to development, it does not require a fork. Branches are typically created within the same repository to work on new features. Forking is used when you need an entirely separate copy of the repository.

Given this information, the correct answers are B and C .

GitHub Projects supports various layouts to help teams organize and visualize their work. The available layouts include:

B.  

Kanban : This is a visual task management tool where tasks are represented as cards and moved across columns that represent different stages of work.

C.  

Board : This layout is similar to Kanban but can be more flexible, allowing users to set up boards in various ways to suit their workflow needs.

D.  

Table : The Table layout allows you to view your tasks in a spreadsheet-like format, making it easy to manage and edit large amounts of data at once.

Roadmap and Backlog are not standard layouts provided by GitHub Projects. While these terms might be relevant in other project management contexts, GitHub Projects specifically offers Kanban, Board, and Table layouts.

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