While merging and rebasing are similar in Git, they serve two different functions. Here’s what you should know to keep your histories as clean or as complete as you like.
git rebase command has a reputation for being magical Git voodoo that beginners should stay away from, but it can actually make life much easier for a development team when used with care. In this article, we’ll compare
git rebase with the related
git merge command and identify all of the potential opportunities to incorporate rebasing into the typical Git workflow.
git branch --merged <BRANCH> | grep -v "<BRANCH>" | xargs -n 1 git branch -D git branch --merged | grep -v "master" | xargs -n 1 git branch -d
don’t forget about
- Show log
--author=""– print commits by pointed user
--name-only– only file name
--oneline– commits comments in one line
--graph– commits tree
--reverse– old commits before new commits
--after– commits after pointed date
--before– commits before pointed date