Skip to main content

Pretty git Log

SO you dislike git log output in console like me and do not use it... Because it looks like so:
How about this one?

It's quite easy...
Just type:

git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --

It may be hard to enter such an easy command every time. Let's make an alias instead... Copypaste this to your terminal:

git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --"

And use simple command to see this pretty log instead:

git lg

Now in case you want to see lines that changed use:

git lg -p
In order for this command to work remove the -- from the end of the alias.

May the code be with you!

NOTE: this article is a rewritten copy of http://coderwall.com/p/euwpig?i=3&p=1&t=git and have been put here only in purpose of note to myself.  However you may use for your own needs...


UPD2: And unless you're a contributor of the git project and have written at least part of original code and/or documentation that does this trick... Then you probably stole the idea. ;) (IMHO)

Comments

  1. I wonder whether it was you who just ripped http://coderwall.com/p/euwpig?i=3&p=1&t=git verbatim or the other way round. One of you is not giving proper credit, though.

    ReplyDelete
    Replies
    1. Thanks for note. Gave a proper credit to author of the idea here... But article is my own experience according to his one..

      Delete
    2. I implemented it as two pieces:

      git config --global alias.graph 'log --format=damn-awesome --graph'
      git config --global pretty.damn-awesome = '%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset'

      Delete
  2. This comment has been removed by the author.

    ReplyDelete
  3. Something else you could try is setting the "format.pretty" config option either globally or local to the repository. That would keep you from having to use an alias.

    ReplyDelete
    Replies
    1. SO setting an alias considered 'bad'? why?

      Delete
    2. If you use both you can clean up a lot the alias definition and can reuse the format definition in other contexts:

      [pretty]
      graph = %Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset

      [alias]
      lg = log --pretty=graph

      Delete

Post a Comment

Popular posts from this blog

Django: Resetting Passwords (with internal tools)

I have had a task recently. It was about adding a forms/mechanism for resetting a password in our Django based project. We have had our own registration system ongoing... It's a corporate sector project. So you can not go and register yourself. Admins (probably via LDAP sync) will register your email/login in system. So you have to go there and only set yourself a password. For security reasons you can not register. One word. First I've tried to find standart decision. From reviewed by me were: django-registration and django password-reset . These are nice tools to install and give it a go. But I've needed a more complex decision. And the idea was that own bicycle is always better. So I've thought of django admin and that it has all the things you need to do this yourself in no time. (Actually it's django.contrib.auth part of django, but used out of the box in Admin UI) You can find views you need for this in there. they are: password_reset password_reset_...

Vagrant error: * Unknown configuration section 'hostmanager'.

Sometimes you get a vagrant environment or boilerplate with a Vagrantfile config in there and do a vagrant up command. And see some errors. like this: There are errors in the configuration of this machine . Please fix the following errors and try again : Vagrant: * Unknown configuration section 'hostmanager'. To fix this one needs: $ vagrant plugin install vagrant - hostmanager Installing the ' vagrant-hostmanager ' plugin . This can take a few minutes . . . Fetching : vagrant - hostmanager - 1.8 .6 . gem ( 100 % ) Installed the plugin ' vagrant-hostmanager (1.8.6) ' ! So command to fix this as follows: vagrant plugin install vagrant-hostmanager