3 ms·
Because very often the client will be some piece of command line tooling that doesn't do those things. https://commit.style https://commit.style > Git is stro
by Reelin 8y ago
Because very often the client will be some piece of command line tooling that doesn't do those things.
https://commit.style https://commit.style
> Git is strongly opinionated that the author is responsible for line breaks; if you omit them, command line tooling will show it as one extremely long unwrapped line.
- int_19h 8y agoThe terminal will still wrap that long line. In general, this approach is broken by design, because the author cannot know where the commit message is going to be displayed. It might actually be in the context where wrapping at 80 or even at 72 is still not long enough (a tooltip in an IDE, say). Or it might be one where it results in a lot of wasted whitespace. It's much better to fix anything that does not handle wrapping properly to do so, than to impose an arbitrary limit that only really works for one environment.