Code review in pull requests in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of git command showing pull request status

What is the output of the following git command when checking the status of a pull request branch locally?

Git

git fetch origin pull/42/head:pr-42
 git checkout pr-42
 git status

A fatal: 'pull/42/head' does not appear to be a git repository

B

On branch pr-42
Your branch is up to date with 'pr-42'.
nothing to commit, working tree clean

C

On branch pr-42
Your branch is based on 'origin/main', but the upstream is gone.
nothing to commit, working tree clean

D

On branch pr-42
Your branch is ahead of 'origin/pr-42' by 1 commit.
nothing to commit, working tree clean

💡 Hint

Fetching a pull request creates a local branch named pr-42 tracking the PR head.

The command fetches the pull request number 42 into a local branch pr-42. Checking out pr-42 puts you on that branch. git status shows 'Your branch is up to date with 'pr-42'.'

🧠 Conceptual

intermediate

Purpose of code review in pull requests

What is the main purpose of performing a code review in a pull request?

A To check code quality, find bugs, and ensure standards before merging

B To deploy the code directly to production

C To automatically merge code changes without human intervention

D To delete the source branch after merging

💡 Hint

Think about why teams review code before merging.

Code review helps catch bugs, improve code quality, and maintain coding standards before merging changes into the main branch.

🔀 Workflow

advanced

Correct order of steps in a pull request review workflow

Arrange the steps in the correct order for a typical pull request code review workflow.

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 1,2,4,3

💡 Hint

Think about the natural flow from coding to review to update.

First, the developer creates and pushes code (1), then opens a pull request (2). The reviewer then comments (3), and the developer updates the PR (4).

❓ Troubleshoot

advanced

Error when merging pull request due to conflicts

You try to merge a pull request but get this error: "Merge conflict in file.txt". What should you do next?

A Delete the pull request and create a new one

B Force push the pull request branch to overwrite conflicts

C Fetch the latest main branch, merge it locally into the PR branch, resolve conflicts, then push

D Ignore the conflict and merge using --no-verify

💡 Hint

Conflicts mean changes clash and need manual fixing.

You must update the PR branch with the latest main branch, fix conflicts locally, then push the resolved code.

✅ Best Practice

expert

Ensuring accessibility in code review comments

Which practice best ensures accessibility when leaving code review comments on UI changes?

A Approve the PR without testing UI accessibility

B Only comment on code style and ignore UI accessibility

C Request the developer to add more animations for better UX

D Check color contrast, keyboard navigation, and ARIA labels in the UI code

💡 Hint

Accessibility means making UI usable for everyone.

Good code review includes checking UI accessibility features like color contrast, keyboard navigation, and ARIA labels.