A convenient way to streamline your Git workflow is by creating aliases for frequently used commands in your .gitconfig file.

Git’s rebase command can be puzzling for newcomers, and its description in the manpage doesn’t offer much clarity

Sometimes, you may want to quickly see what changes have been made as you work. Perhaps you stepped away for a moment and need a refresher

Previously, we covered sharing changes, but that included your repository’s entire history. But what if you only need to export changes from a specific commit or just a particular folder?

Here’s a quick and fascinating tip for today: using git log –graph. If you’re ever puzzled about the direction of branches or how merges were executed

Ever found yourself curious about how many commits you’ve contributed to a project? Or perhaps you’re interested in knowing which colleague has made significant changes

Sometimes, the usual git add . or git commit -am commands just don’t cut it. Perhaps you need to split changes across multiple commits

So, you’re looking to explore your repository in a whole new light. Tired of the command line, you crave graphs, pixels, buttons, and graphics.

I often find myself needing to perform this task when setting up or synchronizing my various machines, yet I always seem to forget the command.