Fork and pull request workflow in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a fork in GitHub?

A fork is a personal copy of someone else's repository. It lets you freely make changes without affecting the original project.

beginner

What is a pull request?

A pull request is a way to ask the original project owner to review and merge your changes from your fork into their repository.

intermediate

Why do we use forks and pull requests instead of pushing directly to the main repository?

Forks and pull requests keep the main project safe. They let others review your changes before adding them, preventing mistakes or unwanted code.

beginner

What is the typical first step after forking a repository?

Clone your fork to your local computer so you can work on the code using Git commands.

beginner

What happens after you create a pull request?

The project maintainers review your changes. They may ask for improvements or approve and merge your code into the main project.

What does a fork create in GitHub?

A A new branch in the original repository

B A backup of your local files

C A personal copy of a repository

D A pull request

A fork creates a personal copy of the repository under your GitHub account.

What is the main purpose of a pull request?

A To clone a repository

B To request merging your changes into the original repository

C To delete a branch

D To create a new repository

Pull requests ask the original project to review and merge your changes.

Which step comes first in the fork and pull request workflow?

A Create a pull request

B Review code

C Merge changes

D Fork the repository

You first fork the repository to create your own copy.

Why is it important to work on a fork instead of the original repository?

A To avoid affecting the original project directly

B To delete the original project

C To speed up cloning

D To create a backup

Working on a fork keeps the original project safe from unwanted changes.

What do maintainers usually do after receiving a pull request?

A Review and decide to merge or request changes

B Delete the fork

C Clone the fork

D Create a new branch

Maintainers review pull requests to ensure quality before merging.

Explain the fork and pull request workflow from start to finish.

Think about the steps you take to contribute to a project you don't own.

Why is the fork and pull request workflow important for collaboration?

Consider how teams avoid mistakes and keep projects organized.