If you’re one of those developers who still don’t use any version control system, I don’t know how you’re still managing to get work done.
In this ...
For further actions, you may consider blocking this person and/or reporting abuse
I think rebase is one thing that should be present in this list.
Personally, I use it quite often and it's really helpful, especially if you work in a team.
And interactive rebase allow to squash commits and keep your history clean and clear.
Totally agree, I use it so often I can't even imagine working without it now.
Definitely! Extremely useful.
Definitely
git add -p
too, for an interactive view of what you've made changes on.This!
git add -p
was probably was helped me the most when swapping Source Tree for CLI git.Always
git add -p
!Also
git diff
, I use this all the time to review changes before committing them.git log --graph
if you want to see the classic git branch timeline view.git log
takes has a huge number of options, I normally use it with:Optionally I also passing
--all
in case I want to see all branches.I like to use
git lg
.coderwall.com/p/euwpig/a-better-gi...
To see history of changes at specific line:-
To see evolution at line 337:-
At Point 10). You can also use "git stash pop" for getting back locally save code.
for your reference find the difference between "git stash apply" and "git stash pop" in below link
stackoverflow.com/questions/152860...
Also , Search
Search the working directory for foo():
Hi Dhruv,
You have shared a nice list of Git Commands, I have shared my own GIT Commands List Please check, if you find anything which is missing from your list, please add them into your websites: techgeekbuzz.com/git-commands/
Definitely git bisect too, I though the idea of commits were cool but was really skeptical of the practicality of using them to debug. git bisect stream lines this very efficiently and is an incredibly useful debugging tool!
i'll add
git reflog
I would replace merge with rebase, but that's just me :-)
amazing post
try
tig
utility, it shows logs in interactive way.A handful of great git commands wesbos.com/git-hot-tips/
How about git commit --interactive ?
Consider better formatting to improve readability. Give examples with fake names or paths.
thanks a lot help