Code review in pull requests in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a pull request in Git?

A pull request is a way to ask team members to review and approve your code changes before merging them into the main project branch.

beginner

Why do we do code reviews in pull requests?

Code reviews help catch mistakes early, improve code quality, share knowledge, and keep the project consistent.

beginner

What should you check during a code review?

Check if the code works as expected, follows style rules, is easy to understand, and does not break anything else.

beginner

How do you leave feedback in a pull request?

You can comment directly on lines of code, suggest changes, or approve the pull request if everything looks good.

beginner

What happens after a pull request is approved?

Once approved, the code changes can be merged into the main branch, making them part of the project.

What is the main purpose of a pull request?

A To review and approve code changes before merging

B To delete old branches

C To create a backup of the repository

D To run automated tests only

A pull request is used to review and approve code changes before merging them into the main branch.

Which of the following is NOT a typical step in a code review?

A Checking code style

B Approving or requesting changes

C Suggesting improvements

D Running the code on a live server without testing

Running code on a live server without testing is risky and not part of a normal code review.

How can you provide feedback on a specific line in a pull request?

A By deleting the pull request

B By commenting directly on that line

C By editing the code yourself without approval

D By sending an email

You can comment directly on specific lines in the pull request to give clear feedback.

What should you do if you find a bug during a code review?

A Delete the pull request

B Ignore it and approve anyway

C Request changes and explain the issue

D Merge the code immediately

You should request changes and explain the problem so the author can fix it.

What happens after a pull request is merged?

A The code becomes part of the main branch

B The code is deleted

C The pull request is reopened automatically

D The repository is archived

Merging a pull request adds the changes to the main branch of the project.

Explain the process and benefits of code review in pull requests.

Think about how teammates check each other's work before adding it to the project.

Describe how you would give constructive feedback during a pull request review.

Imagine helping a friend improve their work kindly and clearly.