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. FresherGitHub Actions Basics

    A job's first step runs npm test and fails because package.json is missing. What is the most likely cause?

    • npm test can only run on Windows runners and not on Linux runners
    • package.json has to be stored inside the .github/workflows folder
    • The job has no actions/checkout step, so the code was never fetched
    • Jobs can read repository files only after a pull request is merged
    Show the answer

    Answer: The job has no actions/checkout step, so the code was never fetched. A runner starts with an empty workspace. actions/checkout clones the repository at the commit that triggered the run, so later steps can see the code. Without it, the steps see no project files at all.

  2. Intermediate (1-5 years)Rewriting History and Reflog

    In the repo app, notes.txt was built by three commits, oldest first: Add notes (line one), Add line two, Add line three (HEAD). Karan forgot to add a test file to the last commit. What does this print?

    echo "def test(): pass" > test_cart.py
    git add test_cart.py
    git commit -q --amend --no-edit
    git rev-list --count HEAD
    git show --name-only --format= HEAD | sort | tr "\n" " "
    • 4 commits; the new last one has only test_cart.py
    • 3 commits; the last one has only test_cart.py
    • 3 commits; the last one has notes.txt and test_cart.py
    • 4 commits; the last one has notes.txt and test_cart.py
    Show the answer

    Answer: 3 commits; the last one has notes.txt and test_cart.py. --amend --no-edit rebuilds the last commit from the current index, which now also holds test_cart.py, and keeps the message. The count stays 3 because the old commit is replaced, not followed; only its id changes.

  3. Experienced (5+ years)Stash and Cherry-pick

    How does Git store a stash entry made with git stash -u?

    • As a commit whose parents are HEAD, an index commit and an untracked commit
    • As a patch file under .git/stash, with one file for every stash entry
    • As a copy of the index saved in .git/index.stash next to the index
    • As a branch named stash/<n> that git branch hides from its listing
    Show the answer

    Answer: As a commit whose parents are HEAD, an index commit and an untracked commit. A stash is a merge-like commit referenced by refs/stash: parent 1 is the HEAD it was made on, parent 2 records the index, and with -u parent 3 holds the untracked files. Older entries live in the refs/stash reflog.

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