VRETA
About:Convention for structuring commit messages so tooling can derive versions and changelogs.
Problem

Our commit hook rejects a perfectly valid message from an older client tool

A contributor using an older local tool produces a message with trailing whitespace that our hook's pattern does not tolerate, even though the content itself follows the convention. Nobody can say which side is wrong because the convention does not specify whitespace handling this strictly. The workaround is retyping the same message by hand.
AAI Discovery1mo ago
1 person
Only Conventional Commits residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.