Pull request process in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this git command after pushing a branch?

You run the following commands:

git checkout -b feature-xyz
git push origin feature-xyz

What is the typical output message you will see after the push completes successfully?

Git

git checkout -b feature-xyz
git push origin feature-xyz

A Switched to a new branch 'feature-xyz'\nEverything up-to-date

B fatal: remote origin already exists.

C Enumerating objects: 5, done.\nCounting objects: 100% (5/5), done.\nDelta compression using up to 8 threads\nCompressing objects: 100% (3/3), done.\nWriting objects: 100% (3/3), 300 bytes | 300.00 KiB/s, done.\nTotal 3 (delta 0), reused 0 (delta 0)\nremote: Resolving deltas: 100% (0/0), done.\nTo github.com:user/repo.git\n * [new branch] feature-xyz -> feature-xyz

D error: failed to push some refs to 'origin'

💡 Hint

Think about what git shows when a new branch is pushed to the remote.

When you push a new branch, git shows the progress of objects being sent and confirms the new branch creation on the remote.

🧠 Conceptual

intermediate

What is the main purpose of a pull request in Git workflows?

Choose the best description of why teams use pull requests.

A To merge code changes directly to the main branch without review.

B To request feedback and review before merging code changes into a shared branch.

C To delete branches that are no longer needed.

D To create a backup of the repository on a remote server.

💡 Hint

Think about collaboration and quality control in teams.

Pull requests allow team members to review code changes, discuss them, and approve before merging to ensure quality and avoid errors.

🔀 Workflow

advanced

What is the correct sequence of commands to create a pull request branch, push it, and open a pull request on GitHub CLI?

Arrange the following commands in the correct order to create a feature branch, push it to origin, and open a pull request using GitHub CLI.

A 1,4,2,3

B 1,2,4,3

C 4,1,2,3

D 1,4,3,2

💡 Hint

Remember you must commit changes before pushing, and open the PR after pushing.

First create and switch to the branch, then add and commit changes, push the branch, then open the pull request.

❓ Troubleshoot

advanced

What error will you see if you try to push a branch without permission to the remote repository?

You run:

git push origin feature-branch

but you do not have write access to the remote repo. What error message will git show?

A error: failed to push some refs to 'origin'\nfatal: unable to access 'https://github.com/user/repo.git/': The requested URL returned error: 403

B fatal: remote origin already exists.

C Everything up-to-date

D fatal: not a git repository (or any of the parent directories): .git

💡 Hint

403 error means forbidden access.

If you lack permission, git returns a 403 HTTP error indicating forbidden access when pushing.

✅ Best Practice

expert

Which option best describes a recommended practice before merging a pull request?

Select the best practice to ensure code quality before merging a pull request into the main branch.

A Delete the feature branch before merging to keep the repo clean.

B Merge immediately after opening the pull request to save time.

C Force push to the main branch to overwrite history.

D Run automated tests and have at least one team member review the code changes.

💡 Hint

Think about quality control and collaboration.

Running tests and peer review help catch bugs and improve code quality before merging.