Working with GIT version control systems always have received a mixed bag of reviews. Some find it really easy and manageable, while others struggle with working with it and look for better updates to the open project.
Today, we’re uncovering the hidden abilities of some of the GIT commands to give you more confidence in working with it. You may also get exposed to the new magical commands.
The following hacks will always keep your mind ready to play with GIT
The hidden abilities of GIT
There will be dark times in your source code committing life- you may even see errors while connecting to GIT. Sometimes the origin for the repository may get reset based on patches updates or windows updates that may ruin your day. Don’t worry, always make sure the configurations are good to go with.
git remote -v will always help you check if the remote configurations are in place or not. If not you can always set the remote url pointing to origin using the following command:
git remote –set-url origin the-remote-url-here
Humans are meant to make mistakes, so do people using GIT. Many-a-times, you might add a file to indexing which you may not want. Undo is the first option that comes to mind. And the GIT community was wise enough to have a managed command ready for us to do that.
git reset /file/path/here
In case, you made a much bigger mistake, that you even committed the code, don’t worry. The following commands will help you here:
git reset --soft HEAD~1
git reset /file/path/here
git rm /file/path/here
In a hurry, it’s easy to forget adding a file to your commit. No worries! The option “amend” has got you covered:
git add /file/path/here
git commit — amend
In case you push something wrongly or in the wrong state on remote, you need to be cautious.
git push origin — delete <branchname> </branchname>
Now go back to your console github/bitbucket, and voila! The branch is no longer in the list. But always remember, any branch you delete on remote is always archived and can be retrieved later. So be cautious before you push something confidential to remote.
Most of the times when you have uncommitted changes, git won’t allow you to pull from remote since the changes may get wrongly overridden. But when you do really meaningful and significant work, you don’t want to revert your changes. But you still want to get the latest pull.
This is a situation that happens everyday in the life of git user. In case you have been away from this, learn the following command:
This would stash your existing changes, without the need to commit them and allowing you to take the latest pull and further work on your own changes too. Told you, this is all magical!
“Did you just merge the branches that weren't required? How can you do that?”
Before your boss asks you these questions, make sure you know that ‘revert’ exists! First, let’s understand how a merge works first. It simply makes the HEAD point to a specific commit. Now you only need to get the HEAD to a better place, where the issues don’t exist.
Run the following command and the HEAD pointer in GIT is back to the right commit you wanted.
git revert HEAD
Reverting commands have many other customizations available, like you can make HEAD point to a particular commit. But now you know, you can revert things back to a stable state and simply dodge most of the issues.
The above mentioned hacks are frequent occurring scenarios in GIT. Once you add them to your bucket, GIT seems simpler.
Get Started With Engati
We hope this blog has helped you understand GIT a little bit more.
Try Engati for free today. No credit card needed.