Conversation
With commit.verbose=true, git appends the staged diff below a scissors line in the edited commit message file. The diff isn't comment-prefixed, so sed '/^#/d' left it in place, right after the header with no blank line, tripping the structure check.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With
commit.verbose=true, git appends the staged diff below a scissors line in the edited commit message file (example). The diff isn't comment-prefixed, sosed '/^#/d'leaves the diff in place, right after the commit header with no blank line, failing the structure check.I tested too by disabling
commit.verboseand it still works.Why ? Because I like being reminded of what I did when typing my commit message 👍
Before
would raise :
After
Commit are working again