Pull request process in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a pull request in Git?

A pull request is a way to ask to merge your code changes from one branch into another, usually from a feature branch into the main branch. It lets others review your changes before adding them.

beginner

Why do teams use pull requests?

Teams use pull requests to review code, catch mistakes early, discuss improvements, and keep the main code safe and clean.

beginner

What are the typical steps in a pull request process?

1. Create a feature branch and make changes.<br>2. Push the branch to the remote repository.<br>3. Open a pull request to merge changes.<br>4. Team reviews the code.<br>5. Address feedback and update the pull request.<br>6. Merge the pull request when approved.

intermediate

What happens if reviewers request changes on a pull request?

You update your code on the same branch, push the changes, and the pull request updates automatically. Reviewers then check the new changes.

beginner

What is the difference between merging and closing a pull request?

Merging adds your changes to the target branch. Closing without merging means your changes are not added and the pull request is discarded.

What is the first step to start a pull request?

A Create a feature branch and make changes

B Merge the main branch

C Delete the repository

D Close an existing pull request

You start by creating a feature branch and making your code changes there before opening a pull request.

Who usually reviews a pull request?

A Random internet users

B Team members or collaborators

C Only the person who created it

D The operating system

Team members or collaborators review pull requests to ensure code quality and correctness.

What should you do if your pull request gets feedback requesting changes?

A Create a new repository

B Delete your branch immediately

C Update your code and push changes to the same branch

D Ignore the feedback

You update your code on the same branch and push the changes; the pull request updates automatically.

What does merging a pull request do?

A Deletes your feature branch

B Creates a new branch

C Closes the repository

D Adds your changes to the target branch

Merging adds the changes from your feature branch into the target branch, usually main or master.

What happens if you close a pull request without merging?

A Your changes are not added to the target branch

B Your changes are merged automatically

C Your branch is deleted

D The repository is archived

Closing without merging means your changes are discarded and not added to the target branch.

Explain the pull request process from creating a branch to merging changes.

Think about the steps you take to safely add your code to the main project.

Why is code review important in the pull request process?

Consider how teamwork helps make better software.