ProDeveloperTutorial.com

Tutorials and Programming Solutions
Menu
  • Shell Scripting
  • System Design
  • Linux System Programming
  • 4g LTE
  • Coding questions
  • C
  • C++
  • DSA
  • GIT
  • 450 DSA Cracker
  • 5G NR
  • O-RAN

Chapter 8: GIT correction commands

prodevelopertutorial August 3, 2020

In this chapter we shall learn about below topics:

git revert
git bisect
git grep
git reset

git revert

“git revert” is similar to “git reset”. But we use git revert, when the changes are already committed to remote repository.

Suppose you have committed 3 times and you need to change something in the third last commit.

Now in the usual flow, when you fix the changes and commit, it will usually create a new index. If you dont want that, you can use “git revert” command.

Example:

git revert HEAD~2

The above command specifies to revert the changes specified by 3rd last commit in the head and create a new commit with reverted changes.

git bisect

Suppose you have done multiple commits. And from one commit, there is an issue introduced.

One way to find the issue is to roll back and then checkout from which commit the issue is introduced.

For that you need to apply divide and conquer technique. So “git bisect” does the exactly that.

“git bisect” is used to perform binary search to find the commit that introduced a bug.

You will start the bisecting by using “git bisect start” command.

Now you can tell git regarding the bad commit reference as “git bisect bad HEAD”

And then you need to give the good commit as “git bisect good 78rehjsd789jjh3289”

Now git will give you the number of revisions.

Then again you perform the same above steps, till you find the code of a bad commit.

To stop bisecting use “git bisect reset” command.

git grep

If you are aware of linux grep command, then there is no difference between “grep” and “git grep”.

The only difference is “git grep” fill search only files tracked by git.

Normal grep will search all the files in that directory.

Example:

“git grep foo”

git reset

You are working on a feature and suppose that feature got changed before the commit happened and now you need to revert all the changes.

Instead of pulling new view, you can revert back the changes made to the files by using “git reset” command.

There are 2 reset command.

Soft reset and hard reset.

For hard reset use “git reset –hard HEAD” command. It will resets the index and working tree. So the changes to tracked files in the working tree since commit are discarded.

For soft reset use “git reset –soft HEAD” command. It will not reset the index, but changes all the files to “Changes to be committed”.

Share
Email
Tweet
Linkedin
Reddit
Stumble
Pinterest
Prev Article
Next Article

About The Author

prodevelopertutorial

Follow this blog to learn more about C, C++, Linux, Competitive Programming concepts, Data Structures.

Leave a Reply Cancel Reply

You must be logged in to post a comment.

ProDeveloperTutorial.com

Tutorials and Programming Solutions
Copyright © 2023 ProDeveloperTutorial.com
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Do not sell my personal information.
Cookie SettingsAccept
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
SAVE & ACCEPT