Community
Participate
Working Groups
It seems that the Staging view enforces a maximum line length and then inserts a line break. This is intrusive. Text wrapping looks strange. See the effect of creating long lines in the attached screenshot. I do acknowledge the various styles that are being used [1][2] but I would like to see a more friendly implementation. Proposals: 1. Add a rule to the Staging view preferences with default e.g. 50/72 2. Let the user write long lines with automatic wrapping When committing, the text will be split according to the active rule and when re-displaying (e.g. when amending) then the text will be combined again. I believe we can use the RFC3676 as an inspiration to make this happen. [3] [1] https://chris.beams.io/posts/git-commit/ [2] https://stackoverflow.com/questions/2290016/git-commit-messages-50-72-formatting [3] https://www.ietf.org/rfc/rfc3676.txt
Created attachment 276154 [details] Git staging view anomalies
You can disable the hard wrapping in the preferences: Team->Git->Committing See attachment. I would suggest changing the default so that it doesn't automatically wrap the lines in the editor though.
Created attachment 276169 [details] Preference for hardwrapping of commit messages