Pushing new branches to remote in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What command do you use to push a new local branch to a remote repository?

Use git push -u origin <branch-name> to push a new local branch to the remote repository and set it to track the remote branch.

beginner

What does the -u flag do when pushing a new branch?

The -u flag sets the upstream (tracking) reference, so future git push and git pull commands know which remote branch to interact with by default.

intermediate

How can you check which remote branches your local branches are tracking?

Run git branch -vv to see local branches with their tracking remote branches and last commit info.

beginner

If you create a new branch locally but forget to push it, what happens when you run git push?

Git will not push the new branch because it has no upstream set. You must push it explicitly with git push -u origin <branch-name> the first time.

beginner

Why is it important to push new branches to the remote repository?

Pushing new branches shares your work with others and backs up your changes. It also allows collaboration and code review on that branch.

Which command pushes a new branch named 'feature' to the remote and sets it to track?

A git push feature

B git push origin

C git push -u origin feature

D git push -u feature origin

The correct syntax is git push -u origin feature to push and set upstream tracking.

What does 'origin' usually refer to in git commands?

A The default name for the remote repository

B The local branch name

C The commit hash

D The current directory

'origin' is the default name git gives to the remote repository you cloned from.

If you run git push without -u on a new branch, what happens?

A Push fails because no upstream is set

B Push succeeds and sets upstream automatically

C Push deletes the branch

D Push merges branches

Without upstream set, git does not know where to push the new branch, so push fails.

How do you see which remote branch your local branch is tracking?

A git log

B git status

C git remote -v

D git branch -vv

git branch -vv shows local branches with their tracking remote branches.

Why might you want to push a new branch to remote early?

A To delete the branch

B To share work and enable collaboration

C To reset the repository

D To change the commit history

Pushing early shares your work and allows teammates to review or contribute.

Explain the steps and command to push a new local branch to a remote repository and set it to track the remote branch.

Think about how to share your new work with others using git.

Describe what happens if you try to push a new branch without setting upstream tracking and how to fix it.

Remember the role of the -u flag.

Practice

1. What is the correct command to push a new branch named feature1 to the remote repository?

easy

A. git push origin new feature1

B. git push origin feature1

C. git push new feature1

D. git push feature1 origin

Solution

1. Step 1: Understand the git push syntax

   The correct syntax to push a branch is git push origin <branch-name>.

2. Step 2: Apply the branch name

   Replace <branch-name> with feature1, resulting in git push origin feature1.

3. Final Answer:

   git push origin feature1 -> Option B

4. Quick Check:

   Push new branch = git push origin branch-name [OK]

Hint: Use 'git push origin branch-name' to push new branches [OK]

Common Mistakes:

• Swapping origin and branch name order
• Adding extra words like 'new'
• Forgetting to specify the remote 'origin'

2. Which of the following commands correctly pushes a new branch dev to the remote named origin?

easy

A. git push origin/dev

B. git push origin:dev

C. git push dev origin

D. git push origin dev

Solution

1. Step 1: Recall the correct push syntax

   The command to push a branch is git push origin <branch-name>.

2. Step 2: Match the branch and remote

   Here, origin is the remote and dev is the branch, so git push origin dev is correct.

3. Final Answer:

   git push origin dev -> Option D

4. Quick Check:

   Push syntax = git push origin branch [OK]

Hint: Remember: remote first, then branch name [OK]

Common Mistakes:

• Using colon instead of space between remote and branch
• Swapping remote and branch order
• Using slash notation incorrectly

3. Given the commands:

git checkout -b featureX
# make some changes
git add .
git commit -m "Add featureX"
git push origin featureX

What will be the result of the last command?

medium

A. The new branch featureX is created and pushed to the remote repository.

B. An error because the branch featureX does not exist locally.

C. Nothing happens because the branch is not checked out.

D. The changes are pushed but the branch is not created remotely.

Solution

1. Step 1: Analyze branch creation and commit

   The command git checkout -b featureX creates and switches to the new branch featureX. Then changes are added and committed.

2. Step 2: Understand the push effect

   git push origin featureX pushes the new branch featureX to the remote, creating it there.

3. Final Answer:

   The new branch featureX is created and pushed to the remote repository. -> Option A

4. Quick Check:

   Push new branch after commit = branch created remotely [OK]

Hint: Push after commit creates branch remotely [OK]

Common Mistakes:

• Assuming branch must exist remotely before push
• Forgetting to commit before pushing
• Thinking push only updates existing branches

4. You run git push origin new-feature but get an error: error: src refspec new-feature does not match any. What is the most likely cause?

medium

A. You forgot to create or checkout the branch new-feature locally.

B. The remote repository origin does not exist.

C. You have uncommitted changes in your working directory.

D. You need to use git push -u origin new-feature instead.

Solution

1. Step 1: Understand the error message

   The error means Git cannot find a local branch named new-feature to push.

2. Step 2: Identify the cause

   This usually happens if the branch was never created or checked out locally before pushing.

3. Final Answer:

   You forgot to create or checkout the branch new-feature locally. -> Option A

4. Quick Check:

   Branch must exist locally before push [OK]

Hint: Create or checkout branch before pushing [OK]

Common Mistakes:

• Assuming push creates branch locally
• Ignoring error and retrying same command
• Confusing remote existence with local branch

5. You have a local branch release with new commits. You want to push it to remote origin and set it to track the remote branch. Which command should you use?

hard

A. git push origin release

B. git push origin -u release

C. git push -u origin release

D. git push --set-upstream release origin

Solution

1. Step 1: Understand tracking branches

   To set the local branch to track the remote branch, use the -u or --set-upstream option with git push.

2. Step 2: Apply correct syntax

   The correct syntax is git push -u origin release which pushes and sets upstream tracking.

3. Final Answer:

   git push -u origin release -> Option C

4. Quick Check:

   Use -u to set upstream tracking [OK]

Hint: Use 'git push -u origin branch' to set tracking [OK]

Common Mistakes:

• Placing -u after remote and branch incorrectly
• Using --set-upstream with wrong argument order
• Forgetting to set upstream and needing manual tracking