Allow Customization of Summary Character Length
As discussed here -
https://stackoverflow.com/questions/69706975/how-to-extend-gitkraken-commit-summary-length
It would be nice to allow customization of the commit editor in a way that (by repo, team, etc.) allows for the summary field to allow more than 72 characters.
Comments: 5
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
17 Jun, '25
Daniel DemusHighlighted comment
Especially now, with forge actions that use the contents of the title to validate a bunch of external things such as jira issue state or filesystem locations for the code being merged from a module-name prefix, a hard-coded limit that breaks the forge workflow is becoming exceedingly undesirable.
You could add ignore patterns for the meta-data parts being counting or you could just make the size configurable per repo. -
08 Dec, '21
BoboWe would also like to be able to use more than 72 characters as we have specific requirements in how we fill out the "Summary" field. These requirements usually take 20 to 30 characters by themselves which leaves us with very few characters to write our actual commit summary.
It would be a great help to us if we could toggle this restriction on and off in our preferences.
Best Regards, -
04 Feb, '22
Shawn FumoJust to add, our team would like to have a limit of 52. It'd be nice if it could show that in the UI, vs having to remember to stop at 20 chars left. Seems like it'd be a very easy preference to add.
-
20 Mar, '24
SovicaPlease extend commit message length. Philosophy aside, this is too short for practical purposes.
We find ourselves switching to other client just to commit with longer messages, very annoying.