My Absolute Must to Have Git Shortcuts

Almost every developer who once started to use Git as a version control system knows how efficient you can be in the console with this tool. With very short commands one is able to check-in and check-out code faster than you think.

All needed steps to interact with your code repository can be executed on command line. There is no need to use any klikibunti ( Wikipedia 2018) (means some kind of graphical user interface) GUI. But with a right .gitconfig  file in our home directory (~) you can even become faster, much faster! But first things first

.gitconfig File

The .gitconfig file allows the user to make some personal settings which affect git and the way how you can work with the version control system (VCS). Since, I am using git for several years in different project I started to define my own aliases for the standard git commands. Aliases allow you to find a more handy substitution for the standard git commands. So instead of writing git commit -a -m "some nice commit message" you could define e.g. git cam "some nice commit message.

Better Logs

These aliases allow me to find things faster in the log. The commands shows the revision graph. Quite equivalent to that what the GUIs  gives you.

Faster Integration

The must to have commands. All standard just add in your [alias] and test these commands:

Pocket Knife

My personal (Swiss) pocket knife. If you do not know where you find a file, e.g. class, package, config, whatever, you can use these commands to find it.


If you are more interested in the content you can use another command. This will grep all files and there lines where your search terms can be located:

Let’s search for the string „abort“

Your Reminder

Have you forgotten an alias? No problem! Just list your settings with:

Wikipedia, 2018, ‘Klickibunti’, Wikipedia, accessed February 2018, from <>.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.