re: Git commits: An Effective Style Guide VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Great article Paul! I see you value a more fully featured, descriptive commit message. I've worked with a few developers who really push for short...
 

Ideally you'd do both: a concise commit subject that summarises the whole change, and a commit body that explains the why of your change. The body is something people will rarely read, but they'll really appreciate it when it answers their questions (they've likely come to your commit message to clarify something).

eg. this commit.

code of conduct - report abuse