Pushing new branches to remote in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of pushing a new branch to remote?

You created a new branch named feature-x locally. You run git push origin feature-x. What is the expected output?

Git

git push origin feature-x

A fatal: remote origin already exists.

B

error: src refspec feature-x does not match any.
fatal: failed to push some refs to 'github.com:user/repo.git'

C Everything up-to-date

D

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 350 bytes | 350.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: 
remote: Create a pull request for 'feature-x' on GitHub:
remote:   https://github.com/user/repo/pull/new/feature-x
To github.com:user/repo.git
 * [new branch]      feature-x -> feature-x

💡 Hint

Think about what happens when you push a branch that exists locally but not yet on remote.

When you push a new branch, git uploads the commits and creates the branch on the remote. The output shows the upload progress and confirms the new branch creation.

🧠 Conceptual

intermediate

Why do you need to push a new branch explicitly to remote?

You created a new branch locally but your teammate cannot see it on the remote repository. Why is pushing the new branch necessary?

A Because pushing deletes the branch from local.

B Because git automatically pushes all branches when you commit locally.

C Because branches are local by default and must be pushed to be visible on remote.

D Because remote repositories do not support branches.

💡 Hint

Think about the difference between local and remote repositories.

Branches exist locally until you push them. Only then do they appear on the remote repository for others to access.

❓ Troubleshoot

advanced

What error occurs if you try to push a branch that does not exist locally?

You run git push origin feature-y but you never created feature-y locally. What error will git show?

Git

git push origin feature-y

A

error: src refspec feature-y does not match any.
fatal: failed to push some refs to 'origin'

B Everything up-to-date

C fatal: remote origin already exists.

D fatal: could not read Username for 'https://github.com': No such device or address

💡 Hint

Check if the branch exists locally before pushing.

Git cannot push a branch that does not exist locally, so it reports the src refspec does not match any.

🔀 Workflow

advanced

What is the correct sequence to create and push a new branch to remote?

Arrange the steps in the correct order to create a new branch feature-z and push it to remote.

A 3,4,1,2

B 1,3,4,2

C 1,4,3,2

D 3,1,4,2

💡 Hint

You must create the branch first, then add and commit changes, then push.

First create and switch to the branch, then stage and commit changes, finally push the new branch to remote.

✅ Best Practice

expert

Which command safely pushes a new branch and sets upstream tracking in one step?

You want to push your new branch feature-new to remote and set it to track the remote branch automatically. Which command achieves this?

A git push -u origin feature-new

B git push origin feature-new --force

C git push origin feature-new:feature-new

D git push origin --all

💡 Hint

Look for the option that sets upstream tracking.

The -u or --set-upstream flag sets the local branch to track the remote branch after pushing.