[oerpli]

I think it doesn't count characters in the body but I am sure Dan could add this as optional feature (though I think it's a bad idea to enforce 80 chars there. Maybe a max line length would be better).

Also, I think it doesn't enforce the limits but counts down letters and if you're above the 50 chars for the message it shows a negative char count in bright red (which makes me reconsider what I want to tell my coworkers in that message).

The other points should be fulfilled.

[Night_Thastus]

My statement about the character limits was incorrect and ambiguous. Git-cola is similar. It displays the number of characters and a color. No color for up to 64, yellow to 72, orange to 78, and red above that.

The body wraps the next word onto a new line if it crosses past 72 characters. (By default, that is configurable and disable-able)

Those are fairly arbitrary choices, but they work well enough for me in practice and help keep my titles/messages clean and readable.

If Fork could do something similar (the auto-wrapping and title warning) I'd be happy.

[DanPristupov]

Enable 'monospace font in commit description' in Fork preferences and set the guideline for the description width. You can wrap the commit message using the context menu option in the description field.

[Night_Thastus]

I've gone ahead and downloaded/installed git-fork and did some brief testing with the features I use most in my existing client. I've sent feedback based on that.

Thanks for your support!

[DanPristupov]

Fork can show the width guideline in the description field if you enable 'monospace font' in preferences. The width is configurable.