Git plays a major role in various organizations as it is one of the best source code management system. There are more than 40 million Git users in the world today. With features such as task management and bug tracking, Git is an efficient technology used by most industry experts today. After conducting several discussions and research, we have compiled the following list of Git interview questions:
Q1. What are Git and GitHub?
Q2. What is the difference between Git and GitHub?
Q3. What is a Git repository? Name some popular Git hosting services.
Q4. What is a version control system? Mention its types.
Q5. What are the main differences between Git and SVN?
Q6. What are the advantages of using GIT?
Q7. What language is used in GIT?
Q8. What are the advantages of Git over SVN?
Q9. What is Git Bash?
Q10. What is the meaning of “Index” or “Staging Area” in GIT?
The Git Interview Questions blog is categorized into the following three parts:
Watch this Git Tutorial Video
Basic Interview Questions
1. What are Git and GitHub?
Git is an open-source and free distributed version control system developed to handle projects of all sizes quickly and efficiently.
GitHub uses Git to provide Internet hosting for version control and software development. It offers the functionality of distributed version control and source code management, which is found in Git, in addition to other unique features.
Check out our blog to learn more about Commands in Git!
2. What is the difference between Git and GitHub?
Git is a version control system that is used in the management of the source code history. GitHub, on the other hand, is a cloud-based hosting service that is used in the management of Git repositories. GitHub is designed to help in the better management of open-source projects.
3. What is a Git repository? Name some popular Git hosting services.
Repositories contain a batch of files that are different versions of a project. These files are imported from the repositories into the local servers of users for further modifications and updates in the content.
A few popular Git hosting services are:
The GIT Cheat Sheet by Intellipaat comes in handy while studying GIT.
4. What is a version control system? Mention its types.
A version control system (VCS) is a software tool used to create different project versions and store them in a repository. All modifications to the code are recorded and tracked by the VCS.
Types of version control systems:
- Local version control systems have a database that maintains all the file changes on disk under revision control in a special format.
- Centralized version control systems contain one repository, and each user gets their own working copy.
- Distributed version control systems contain multiple repositories, each accessible to separate users with their own working copy.
5. What are the main differences between Git and SVN?
|Type of version control
|Access to networks
|Global revision number
||Cryptographic SHA-1 Hash
||No hashed content
Here we list some of the most important differences between Git and SVN:
- When it comes to handling large files, Git is not preferred but SVN can handle multiple projects in the same repository
- Git does not have ‘commits’ across multiple branches but SVN lets you create the folders on any location in the repository layout
- You cannot commit changes in Git but SVN lets you create a tag as a branch and you can create multiple revisions under a root tag
6. What are the advantages of using GIT?
Here are some of the most important advantages of Git:
- Data redundancy and data replication is possible
- It is a highly available service
- For one repository we can have only one directory of Git
- The network performance and disk utilization are excellent
- It is very easy to collaborate on any project
- We can work on any sort of project within the Git
7. What language is used in GIT?
C is the programming language that is used for creating Git which ensures that the overheads are reduced.
8. What are the advantages of Git over SVN?
Since Git is an open source version control system it lets us run multiple versions of our project so that it shows the changes that are made to the code over time and if needed we can keep track of the changes that we have made. This means that a large number of developers can make their own changes and upload those changes so that the changes can be attributed to the particular developers.
9. What is Git Bash?
Git Bash is an application that installs Bash, Git, and a few Bash utilities that are commonly used on a Windows OS. In Git Bash, interaction is possible with Git elements and the repository through different commands.
10. What is the meaning of “Index” or “Staging Area” in GIT?
When we are making the commits, we can make changes to it, format it and review it in the intermediate area known as ‘Staging Area’ or ‘Index’.
11. What is tagging in Git?
Tagging allows developers to mark all the important checkpoints through the course of their projects’ progress. Instead of commit IDs, tag names can be used while commits are checked out and pushed to a remote repo.
12. What is forking in Git?
A repository copy is called a fork. So, forking allows one to experiment with changes without worrying about the original project. This process is ideal for proposing changes to someone else’s projects.
13. What is the use of a Git clone?
The Git clone command lets us copy the existing Git repository. If we want to get a copy of the central repository then the best way to do it is using ‘cloning’.
14. What is the function of ‘git config’?
The ‘Git config’ is a great way to configure our options for the Git installation. Using this command, we can define the repository behavior, preferences and user information.
Intermediate Interview Questions
15. What is the process for creating a repository in Git?
If we want to create a repository in Git, then we need to run the command “git init”. With this command .git repository, we can create a directory in the project directory.
16. What is cherry-pick in Git?
Git cherry-pick is a command that allows the picking of arbitrary Git commits by reference and adding them to the HEAD. Cherry-picking is the process of picking a commit from one branch and applying it to another. It helps in undoing changes.
17. What is origin in Git?
Origin refers to the remote repository that a project was originally cloned from and is used instead of the original repository’s URL. This allows for easier referencing.
18. What is the git push command?
The git push command is applied for uploading content to a remote repository from a local repository. Pushing can overwrite changes, so it should be used with caution.
19. What is the git pull command?
The git pull command is for fetching and downloading content from a remote repository and integrating it with a local repository.
20. What is the difference between git fetch and git pull?
Git fetch retrieves new data from a remote repository but does not integrate it into our working files. It helps in checking if any changes happened in the remote repository. It does not manipulate or destroy anything in the process.
Git pull, on the other hand, updates the HEAD with the latest changes from the remote server and directly integrates it into the working copy files. Using git pull can end in merge conflict as it tries to merge remote changes with the local ones.
21. Explain git checkout in Git.
Git checkout allows for the switching of the HEAD. It can be used to restore the historic versions of files as well. The command operates upon files, commits, and branches.
22. What does git rebase do?
Rebasing is the reapplying of commits on top of another base trip. A sequence of commits is applied from distinct branches into the final commit. It is a linear process of merging and an alternative to the git merge command. Rebasing makes it seem like one has created a branch from a different commit.
23. What is the difference between git rebase and git merge?
In git rebase, a feature branch is moved into a master. Git merge maintains the history by adding a new commit.
24. What is revert in Git?
The git revert command is a forward-moving undo operation. It is a safe way to undo changes as it will create a new commit that inverses the changes instead of deleting or orphaning commits in the commit history.
25. What is the difference between resetting and reverting?
While git reset changes the state of the branch to a previous one by removing all of the states after the desired commit, git revert does it through the creation of new reverting commits and keeping the original one intact.
26. What is the difference between ‘git remote’ and ‘git clone’?
Git remote adds a reference to a remote repository for further tracking. Git clone, like its name, clones an existing remote repository and builds a new one.
27. What is GIT stash?
The Git stash will take the working directory in the current state and index it to put on the stack at a later stage so that what we get is a clean working directory.
This means that if we are in the middle of some task and need to get a clean working directory and simultaneously we want to keep all our current edits, then we can use the Git stash.
28. How are fork, branch, and clone different from each other?
Forking creates a copy of the original repository, and it remains in the GitHub account. Whereas, in cloning, the repository is copied to the local machine using Git. Forking is used to propose changes to the repository owners. In cloning, the changes are directly pushed to the original repository, provided the user has write access. A branch occurs within a repository and is a way to keep developing and modifying the software without affecting the main project.
29. What is the difference between git reflog and log?
The git log is a public record of the commit history for a branch. Reflog, on the other hand, is a private one of the repository’s local commits.
Unlike reflog, the git log is a part of the Git repository and is replicated after a push, fetch, or pull. A developer cannot access a local repository’s reflog without having access to the computer where it is located.
30. What is GIT stash drop?
When we are finished with working on the stashed item or want to remove the list, we can use the Git stash drop. This will ensure that the item that is last added by default or any particular item can be removed from the argument.
31. How to identify if a certain branch has been merged into master?
Git branch –merged master – shows all branches that are merged into master
Git branch – merged – shows all branches that are merged into the head
Git branch – no-merged –shows all the branches that are not merged
32. Why do we need branching in GIT?
With the help of branching, we can have our own branch and we can also jump between various branches. We can go to our previous work, at the same time keeping our recent work intact.
Advanced Interview Questions
33. What are the constituents of the commit object contain?
- the state of a project at a given point of time is contained in a set of files
- Parent object commit references
- A 40-character string that uniquely identifies the commit object called a SHAI name
34. What is HEAD in Git, and how many HEADs can be created in a repository?
The reference to a commit object is called the HEAD. Every repository has a ‘Master’ which is the default head. There can be multiple heads in a repository.
35. What is the regular way for branching in GIT?
The best way to create a branch in GIT is to have one ‘main’ branch and then create another branch for implementing the changes that we want to make. This is extremely useful when there are a large number of developers working on a single project.
36. State a way to create a new branch in Git.
If we want to create a new feature into the main branch, then we can use the command ‘git merge’ or ‘git pull’.
37. How do you define a ‘conflict’ in git?
If we want to merge a commit there is a change in one place and the same change already exists then while merging the Git will not be able to predict which is the change that needs to be taken precedence.
38. How to resolve a conflict in Git?
If we want to resolve a conflict in Git, then we need to edit the files for fixing the conflicting changes and then we can run “git add” to add the resolved files and after that we can run the ‘git commit’ for committing the repaired merge.