You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can sometimes be useful to include compiler output in commit messages, but this is close to impossible due to the commit line length limit of 80 (and inserting your own linebreaks would kind of defeat the purpose of including the output verbatim).
The custom gitlint rule responsible for this only has exceptions for HTTP(S) URLs and Signed-Off-By lines. It might be nice to add a rule that e.g. allows blocks of text delimited by ``` (markdown code blocks) to exceed the line length limit.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
It can sometimes be useful to include compiler output in commit messages, but this is close to impossible due to the commit line length limit of 80 (and inserting your own linebreaks would kind of defeat the purpose of including the output verbatim).
The custom gitlint rule responsible for this only has exceptions for HTTP(S) URLs and Signed-Off-By lines. It might be nice to add a rule that e.g. allows blocks of text delimited by ``` (markdown code blocks) to exceed the line length limit.
Beta Was this translation helpful? Give feedback.
All reactions