4
163
Fork
You've already forked Gitte
16

Commit message summary and description length limits indications #183

Closed
opened 2026年07月10日 07:01:36 +02:00 by nekohayo · 2 comments

In version 0.8.1, I didn't see any visual indications when I was exceeding line length conventions for commit messages.

It would be good for Gitte to help people follow the traditional git commit messages etiquette, as summarized in https://handbook.gnome.org/development/commit-messages.html for example, including:

Summary line

[...]
Be sure to not exceed 72 characters; you can use ‘&’ instead of ‘and’ so the message gets shorter.
[...]

(Traditionally in git the summary line is supposed to be 50 characters or less, but I agree that this limit is very restrictive and 72 characters is fine if it is not possible to shorten to 50)

Main description

[...]
Each line must not exceed 75 characters. There is no limit on the number of lines.
[...]

The "Commit" app does this, and so does Gitg. Gitg shows a margin in the background for the 72 characters limit, and highlights in a more obvious way than "Commit" when you exceed a line's limit:

image

Maybe it could even use two tones of highlighting, i.e. yellow for 50 to 72 and orange/red "above 72"...

The "Commit" app also does automatic line wrapping for you,
though that can be annoying for those rare folks like me
who consider semantic manual line wrapping to be an art form ;)

In version 0.8.1, I didn't see any visual indications when I was exceeding line length conventions for commit messages. It would be good for Gitte to help people follow the traditional git commit messages etiquette, as summarized in https://handbook.gnome.org/development/commit-messages.html for example, including: > ## Summary line > > [...] > Be sure to not exceed 72 characters; you can use ‘&’ instead of ‘and’ so the message gets shorter. > [...] (Traditionally in git the summary line is supposed to be 50 characters or less, but I agree that this limit is very restrictive and 72 characters is fine if it is not possible to shorten to 50) > ## Main description > > [...] > Each line must not exceed 75 characters. There is no limit on the number of lines. > [...] The "[Commit](https://flathub.org/en/apps/re.sonny.Commit)" app does this, and so does Gitg. Gitg shows a margin in the background for the 72 characters limit, and highlights in a more obvious way than "Commit" when you exceed a line's limit: ![image](/attachments/e8fc2c56-601d-4a70-bb25-67805721aa91) Maybe it could even use two tones of highlighting, i.e. yellow for 50 to 72 and orange/red "above 72"... The "Commit" app also does automatic line wrapping for you, though that can be annoying for those rare folks like me who consider semantic manual line wrapping to be an art form ;)
9.3 KiB

This is already implemented for 0.9.0 (will be released Friday, 17th of July), see #120 for reference :-)

Screenshot From 2026年07月10日 07-11-01

This is already implemented for 0.9.0 (will be released Friday, 17th of July), see #120 for reference :-) ![Screenshot From 2026年07月10日 07-11-01](/attachments/9689ccfe-7dbc-4ab2-89f4-661f4e2f73cc)

Oh great! I hadn't seen that one. Thanks!

Oh great! I hadn't seen that one. Thanks!
Sign in to join this conversation.
No Branch/Tag specified
main
next
0.8.1
0.8.0
0.7.2
0.7.1
0.7.0
0.6.1
0.6.0
0.5.0
0.4.1
0.4.0
0.3.0
0.2.0
0.1.10
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ckruse/Gitte#183
Reference in a new issue
ckruse/Gitte
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?