When a pre-commit hook is set up to validate commit message, it can be bypassed by clicking the dropdown menu next to the commit button and choosing the option that indicates --no-verify.
This dropdown menu does not appear if there are no changes from the merge.
Steps to reproduce
Merge branch A into branch B with no changes resulting from the merge
Pre-commit hook rejects commit message
Unable to indicate --no-verify
Expected behavior
Should be able to indicate --no-verify like when a commit is made that does have changes
Screenshots
Expected (does not appear if the "1 file changed" is not present):
Version info
Description
When a pre-commit hook is set up to validate commit message, it can be bypassed by clicking the dropdown menu next to the commit button and choosing the option that indicates
--no-verify.This dropdown menu does not appear if there are no changes from the merge.
Steps to reproduce
--no-verifyExpected behavior
--no-verifylike when a commit is made that does have changesScreenshots
Expected (does not appear if the "1 file changed" is not present):