Git

How to answer in an interview

Git is a distributed version control system used to track changes in source code over time, allowing multiple developers to collaborate without overwriting each other's work. Being distributed means every developer has a full copy of the project history locally, enabling offline work and robust backups.

Explain like I am 5

Git is like a time machine for your code — it keeps snapshots of every change you make, so you can go back and see or undo anything at any point.

How to answer in an interview

Git is the underlying version control tool that tracks changes to files locally on your machine. GitHub is a cloud-based hosting platform built around Git that adds collaboration features like pull requests, issue tracking, and code review, but similar platforms like GitLab and Bitbucket also exist.

Explain like I am 5

Git is the tool that keeps track of your changes on your own computer. GitHub is a website where you can upload and share that tracked history with other people.

How to answer in an interview

A commit is a saved snapshot of your project's staged changes at a specific point in time, identified by a unique SHA hash and accompanied by a commit message describing the change. Commits form the building blocks of a project's history, and each one points to its parent commit, forming a chain.

Explain like I am 5

A commit is like taking a photo of your work at a certain moment, with a little note explaining what changed since the last photo.

How to answer in an interview

A branch is an independent line of development that lets you work on new features or fixes without affecting the main codebase. You can create a branch, make changes and commits on it, and later merge it back into the main branch once the work is complete and tested.

Explain like I am 5

A branch is like making a copy of your drawing to try out a new idea, without messing up your original drawing, and later combining the good parts back in.

How to answer in an interview

git fetch downloads new commits and updates from a remote repository without merging them into your current branch, letting you review changes first. git pull does a fetch followed immediately by a merge (or rebase, depending on configuration) into your current branch.

Explain like I am 5

git fetch is like checking your mailbox and bringing letters inside without opening them yet. git pull is like checking the mailbox and reading all the letters right away.

How to answer in an interview

git add stages changes, moving them into the staging area to be included in the next commit. git commit saves the staged changes as a permanent snapshot in the local repository history. git push uploads local commits to a remote repository so others can access them.

Explain like I am 5

git add is picking which toys to put in a box. git commit is sealing that box with a label. git push is sending the box to a shared storage room so others can see it.

How to answer in an interview

HEAD is a reference that points to the current commit or branch you're working on in your local repository, essentially indicating 'where you are' in the project's history. Checking out a different branch or commit moves HEAD accordingly.

Explain like I am 5

HEAD is like a bookmark showing exactly which page of the story you're currently reading.

How to answer in an interview

.gitignore is a file that specifies patterns for files and directories that Git should not track or stage, such as build artifacts, dependency folders like node_modules, or environment configuration files containing secrets.

Explain like I am 5

.gitignore is like a 'do not photograph' list you give Git, telling it to skip certain files whenever it takes a snapshot of your project.

How to answer in an interview

Cloning creates a local copy of a repository on your machine, maintaining a connection to the original remote. Forking creates a completely separate copy of a repository under your own account on a platform like GitHub, allowing you to make changes independently and later propose them back via a pull request.

Explain like I am 5

Cloning is bringing a copy of a book home to read and write in your own copy while still knowing it came from the library. Forking is more like getting your very own permanent copy at a whole new address that you fully own.

How to answer in an interview

A pull request is a request to merge changes from one branch, often on a fork, into another branch, typically the main branch of the original repository. It provides a platform for code review, discussion, and automated testing before the changes are accepted and merged.

Explain like I am 5

A pull request is like asking, 'Hey, can you check my homework and let it into the class notebook if it looks good?'

How to answer in an interview

Merge combines the histories of two branches by creating a new merge commit that ties both histories together, preserving the full branching history. Rebase replays your branch's commits on top of another branch, creating a linear history without a merge commit, which can make history cleaner but rewrites commit hashes, so it should be avoided on shared branches.

Explain like I am 5

Merge is like taping two separate storylines together, keeping both paths visible. Rebase is like rewriting your storyline as if it happened right after the other one, making it look like one straight line.

How to answer in an interview

A merge conflict occurs when Git can't automatically reconcile changes made to the same part of a file in two different branches. To resolve it, you open the file, review the conflict markers Git inserts around the competing changes, manually edit the file to keep the desired result, then stage and commit the resolved file.

Explain like I am 5

A merge conflict is like two people editing the same sentence in a shared document at the same time — Git asks you to step in and decide which version, or combination, should stay.

How to answer in an interview

git stash temporarily saves uncommitted changes in your working directory so you can switch branches or pull updates with a clean working tree, without having to commit incomplete work. You can later reapply the stashed changes using git stash pop or apply.

Explain like I am 5

Git stash is like quickly shoving your messy homework into a drawer so your desk looks clean for a moment, and you can pull it back out later to keep working.

How to answer in an interview

git cherry-pick applies the changes introduced by a specific commit from one branch onto another branch, without merging the entire branch history. It's useful when you want just one particular fix or feature from another branch without bringing in unrelated changes.

Explain like I am 5

Cherry-pick is like picking just one specific ingredient out of someone else's recipe and adding it to your own dish, instead of copying the whole recipe.

How to answer in an interview

A git tag marks a specific commit as significant, commonly used to denote release versions like v1.0.0. Lightweight tags are simple pointers to a commit, while annotated tags store additional metadata like the tagger's name, date, and message, and are recommended for official releases.

Explain like I am 5

A tag is like putting a sticky flag on a specific page of your notebook to say 'this is the final version we shipped', so you can always find it again easily.

How to answer in an interview

git reset moves the current branch pointer to a previous commit, optionally modifying the working directory and staging area, and can rewrite history, which is risky on shared branches. git revert creates a new commit that undoes the changes of a specific previous commit without altering existing history, making it safer for shared or public branches.

Explain like I am 5

git reset is like tearing pages out of a notebook to go back in time, changing what actually happened. git revert is like writing a new page that cancels out an old page, without ripping anything out.

How to answer in an interview

A detached HEAD state occurs when you checkout a specific commit instead of a branch, so HEAD points directly to that commit rather than to a branch reference. Any new commits made in this state aren't attached to a branch and can be lost once you switch away, unless you create a new branch to save them.

Explain like I am 5

A detached HEAD is like standing on a random page of a book instead of following a bookmark — if you keep writing notes there and walk away without saving your spot, those notes might get lost.

How to answer in an interview

git reset --soft moves the branch pointer to a specified commit but leaves the staging area and working directory unchanged, keeping your changes staged. --mixed, the default, moves the pointer and resets the staging area but leaves working directory files unchanged. --hard moves the pointer and resets both the staging area and working directory, permanently discarding uncommitted changes.

Explain like I am 5

--soft just rewinds the story bookmark but keeps all your notes ready to use. --mixed rewinds the bookmark and puts your notes back in your bag. --hard rewinds the bookmark and throws away any notes you hadn't saved yet.

How to answer in an interview

git bisect helps find the commit that introduced a bug by performing a binary search through the commit history. You mark a known good commit and a known bad commit, and Git checks out commits in between, asking you to mark each as good or bad, narrowing down the culprit commit in O(log n) steps.

Explain like I am 5

git bisect is like playing a guessing game where you narrow down which exact day something broke, by repeatedly checking the middle point between a day you know was fine and a day you know was broken.

How to answer in an interview

A git submodule allows you to embed one Git repository as a subdirectory inside another, keeping the embedded repository's own commit history separate while still tracking a reference to a specific commit within the parent repository. It's often used to include external libraries or shared code as a dependency.

Explain like I am 5

A submodule is like keeping a whole separate notebook tucked inside your main notebook, where the inner notebook still has its own pages and history, but your main notebook just remembers which exact page it's currently pointing to.