{"id":337,"date":"2023-02-01T09:54:21","date_gmt":"2023-02-01T09:54:21","guid":{"rendered":"https:\/\/santosh-shah.com\/blog\/?p=337"},"modified":"2023-07-13T06:51:49","modified_gmt":"2023-07-13T06:51:49","slug":"git-tips-and-tricks","status":"publish","type":"post","link":"https:\/\/santosh-shah.com\/blog\/git-tips-and-tricks\/","title":{"rendered":"Git tips and tricks"},"content":{"rendered":"\n

Revert last commit in GIT<\/h2>\n\n\n\n

Revert last commit in GIt also knows as delete the last commit that was made intentionally or accidenlty. You can revert commit using following action. <\/p>\n\n\n\n

git reset --soft HEAD~1\ngit reset --hard HEAD~1<\/code><\/pre>\n\n\n\n
\u2013soft will not remove your uncommited code. Again if you replace the same with \u2013hard it is going to replace all the uncommited code in your local<\/p>\n\n\n\n
git reset HEAD~1\ngit push origin master --force<\/code><\/pre>\n\n\n\n
This above code will remove the last commit. However you can still see the files. Now when you make git push origin master with force it is going to delete the last commit from history.<\/p>\n\n\n\n
Undo current git merge<\/h2>\n\n\n\n
git merge --abort<\/code><\/pre>\n\n\n\n
This is going to reset your working copy to whatever state it was in before the merge. That means that it should restore any uncommitted changes from before the merge, although it cannot always do so reliably. Generally you shouldn’t merge with uncommitted changes anyway.<\/p>\n\n\n\n
Sometimes you still need to use git reset --merge<\/code> even in more recent versions. I had git merge --abort<\/code> error out (making no changes) where git reset --merge<\/code> succeeds (and does the right thing) in git 2.2.1.<\/p>\n\n\n\n
git merge --abort # is equivalent to git reset --merge when MERGE_HEAD is present.<\/code><\/pre>\n\n\n\n
Git rebase<\/h2>\n\n\n\n
\/\/ quit any currported or ongoing rebase\ngit rebase --quit\n\n\/\/merge branch\ngit rebase --merge branch-name\n\n\/\/rebase particular commit either drop, etc\ngit rebase -i HEAD~2\n<\/code><\/pre>\n\n\n\n
Reference link<\/a><\/p>\n\n\n\n
Git logs<\/h2>\n\n\n\n
git log --oneline\ngit log --oneline --graph --decorate\n\n\/\/git log with with merge and list of files \ngit log -m --name-only<\/code><\/pre>\n\n\n\n
Above git log –oneline will show list of commits in one line with short id within.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
git logs search and find<\/p>\n\n\n\n
git log --after=\"2021-7-1\" --before=\"2021-7-5\"\ngit log --grep='any commit message word'  <\/code><\/pre>\n\n\n\n
Vi editor<\/h2>\n\n\n\n
hit Esc\ntype :wq\npress enter<\/code><\/pre>\n\n\n\n
It will save the current change and exit the vi editor<\/p>\n\n\n\n
:qa! to exit without saving.<\/p>\n\n\n\n
Recover accidently deleted commits<\/h2>\n\n\n\n
Lets say you accidently delete a commit by using <\/p>\n\n\n\n
git reset --hard old_hash_id<\/code><\/pre>\n\n\n\n
It is simply going to delete all commit that was after this hashId. Now we will use git reflog to get the statement of our git activitites.<\/p>\n\n\n\n
git reflog\n#now get the hashid of HEAD 1 \ngit branch recover-commits hashId_HEAD1\ngit rebase --merge recover-commits<\/code><\/pre>\n\n\n\n
This way you will be able to see all commit including lost commit in your new branch and you can simply merge that branch into new commits with last line. Also you can use git cherry-pick in order to merge only specific commit into your working branch. You need to get the id of that lost commit from new branch you had created and perform the following action.<\/p>\n\n\n\n
git cherry-pick lost-commit-hashID<\/code><\/pre>\n\n\n\n
Git merge with squash<\/h2>\n\n\n\n
git merge feature --squash\ngit commit -m \"feature merge\"\ngit push origin master<\/code><\/pre>\n\n\n\n
git merging with squash will compress multiple commit into one and merge it into current branch.  After running above command for merge with squash you might need to commit with new message to reflect on current branch.<\/p>\n\n\n\n
Filename too long in Git for Windows<\/h3>\n\n\n\n
Git has a limit of 4096 characters for a filename but it is not same for Windows operating system while Git is compiled with msys. It uses an older version of the Windows API and there’s a limit of 260 characters for a filename. <\/p>\n\n\n\n
You can circumvent this by using another Git client on Windows or set core.longpaths<\/code> to true<\/code> as explained in other answers.<\/p>\n\n\n\n
git config --system core.longpaths true<\/code><\/pre>\n\n\n\n
Reference link<\/a><\/p>\n\n\n\n
Issue : Pulling without specifying how to reconcile divergent branches is discouraged<\/h3>\n\n\n\n
git pull origin main --rebase<\/code><\/p>\n\n\n\n
When fast forward merge is not working.<\/p>\n\n\n\n
git pull origin layout --no-ff\n<\/code><\/pre>\n\n\n\n
\n
Track all remote branches GIT<\/a><\/blockquote>