CoreHRx Jobs

Apply in one click, save jobs and take free mock tests.

Register free Log in
Hiring? Post jobs with CoreHRx
My account
user

View & update profile

Git and GitHub mock test: free online practice

15 to 30 random questions in 15 to 30 minutes, by the level you choose: staging, branches, merge vs rebase, undo, remotes, prs and actions. After you submit you get your score, your strong and weak topics, and the right answer with an explanation for every question.

Want to revise first? Read the Git and GitHub interview questions and answers.

Choose your experience

Free with a CoreHRx Jobs account: you will be asked to sign in or create one first.

What does the Git and GitHub mock test cover?

The test covers 14 topics across three levels. Each attempt picks 15 to 30 questions at random, by the level you choose, so every attempt is different.

  • Pull Requests and Forks
  • Remotes, Fetch and Pull
  • Reset, Revert and Restore
  • Commits and History
  • GitHub Actions Basics
  • Merging and Conflicts
  • Stash and Cherry-pick
  • Three Trees and Staging
  • Branches
  • Branching Strategies
  • Rebase
  • Rewriting History and Reflog
  • Ignoring Files
  • Tags

Sample Git and GitHub mock test questions

One question from each level, the way they appear in the test. A new set comes on the 1st of every month. Try it, then open the answer.

  1. FresherRewriting History and Reflog

    Why should you avoid amending a commit that is already pushed to a shared branch?

    • Amend makes a new commit id, so the remote and teammates' clones no longer match
    • Amend merges the remote branch into the commit and adds an extra parent to it
    • Amend deletes the commit on the server at once, so teammates lose it right away
    • Amend only works on commits that were never pushed, and otherwise it just fails
    Show the answer

    Answer: Amend makes a new commit id, so the remote and teammates' clones no longer match. Amend writes a replacement commit with a new id; the old one is still on the server. Pushing now needs --force, which rewrites the branch for everyone who already pulled it. On a shared branch, add a new commit instead.

  2. Intermediate (1-5 years)Stash and Cherry-pick

    In a clean repo on main, what does the last command print (lines joined by then)?

    echo a >> notes.txt
    git stash push -q -m "first"
    echo b >> notes.txt
    git stash push -q -m "second"
    git stash list
    • stash@{1}: On main: second, then stash@{0}: On main: first
    • stash@{0}: On main: second, then stash@{1}: On main: first
    • stash@{0}: On main: first, then stash@{1}: On main: second
    • stash@{0}: On main: second
    Show the answer

    Answer: stash@{0}: On main: second, then stash@{1}: On main: first. The stash is a stack kept in the reflog of refs/stash: the newest entry is stash@{0} and older ones shift down, so first becomes stash@{1}. git stash pop with no argument takes stash@{0}, the last one pushed.

  3. Experienced (5+ years)Tags

    What does git tag -s v2.0 -m 'Release 2.0' add over a plain annotated tag?

    • A checksum of all files that GitHub needs first
    • An encrypted copy of the tagged commit for safety
    • A GPG or SSH signature that git tag -v can verify
    • A lock so that nobody can delete the tag later
    Show the answer

    Answer: A GPG or SSH signature that git tag -v can verify. -s makes an annotated tag and signs it with your key; gpg.format=ssh allows SSH keys. git tag -v v2.0 checks the signature, and GitHub marks it Verified for keys added to the account. It proves who tagged; it does not lock anything.

Take the full Git and GitHub mock test: 15 to 30 questions and 15 to 30 minutes, by level.

How is the Git and GitHub mock test scored?

A question counts as right only when you pick exactly the right option, or all the right options where it says so; a question left blank counts as wrong. Your score is the share of the test's questions you got right (15 to 30, by level). The result also scores every topic, so you know what to revise before the interview.

  • 75% or more in a topica strength
  • 50% to 74%worth a revision
  • Under 50%a topic to work on

Git and GitHub mock test: questions people ask

Is the Git and GitHub mock test free?

Yes. The Git and GitHub mock test is free. You need a free CoreHRx Jobs account to start it, so your score and the topics to work on are saved.

How many questions are in the Git and GitHub mock test?

It depends on the level: Fresher has 15 questions in 15 minutes, Intermediate has 20 questions in 20 minutes, Experienced has 30 questions in 30 minutes. They are multiple-choice questions picked at random from a larger bank of Git and GitHub questions at your level, so every attempt is different.

Which Git and GitHub topics does the test cover?

The questions cover Pull Requests and Forks, Remotes, Fetch and Pull, Reset, Revert and Restore, Commits and History, GitHub Actions Basics, Merging and Conflicts, Stash and Cherry-pick, Three Trees and Staging, Branches, Branching Strategies, Rebase, Rewriting History and Reflog, Ignoring Files, Tags. Your result shows how you did in each topic.

Which level should I choose?

Fresher if you are a student or have less than a year of experience, Intermediate for 1 to 5 years at work, and Experienced for 5 years or more.

Can employers see my Git and GitHub score?

Only your best Git and GitHub score, and only when it is 60% or more. It shows on the job applications you send on CoreHRx. Lower scores stay private.

Can I take the Git and GitHub mock test again?

Yes, up to 10 tests a day. Each attempt picks questions you have not seen recently first.

All mock tests