Write good git commit messages

Re:Write good git commit messages by abhishekjha on Wednesday December 12, 2018 @08:53AM (#18663870)

>This is also the primary reason why I highly dislike merge commits: They make git logs extremely unreadable.

I am new to git. You will have to merge eventually with somebody when you are collaborating. Can you really avoid merge commits?

I don't like how `git reflog` keeps track of which hash did I switch to. I only jump to hashes for a quick run. I don't want it actually tracking that in the log. Does anybody know how to avoid that as well?

[ Parent | on HN ]

Re:Write good git commit messages by nordsieck on Wednesday December 12, 2018 @08:57AM (#18663903)

>> This is also the primary reason why I highly dislike merge commits: They make git logs extremely unreadable.

> I am new to git. You will have to merge eventually with somebody when you are collaborating. Can you really avoid merge commits?

Many developers prefer to only rebase, such that master looks like a single chain of commits without any branching or other administrative structure.

[ Parent | on HN ]

Re:Write good git commit messages by aviraldg on Wednesday December 12, 2018 @08:57AM (#18663896)

Yes, you can rebase: https://www.atlassian.com/git/tutorials/merging-vs-rebasing

(best used with --ff-only in your config to avoid unnecessary/unintentional merge commits)

[ Parent | on HN ]

Re:Write good git commit messages by drums8787 on Wednesday December 12, 2018 @05:10PM (#18668183)

Agree, learn to rebase well. Having a chain of atomic, well commented commits is bliss.

[ Parent | on HN ]