fix: handle commit message format errors#69
Merged
Conversation
Owner
Author
|
@tsmalls93 , I think this was the problem you mentioned on #66 . It would be nice if we could reproduce that situation in a test case .I will think about one. If you have an idea , id be glad to hear it. |
Signed-off-by: Nico <rainbowstack@gmail.com>
bluebrown
force-pushed
the
fix/commitmsg-error
branch
from
0bef24d to
8d9793e
Compare
Owner
Author
|
@rossigee , you can try the changes with this image https://hub.docker.com/layers/bluebrown/kobold/1971e78/images/sha256-13b9b1f161038442f710a0a6661e144d96560a5dd67cf9cb5edb574511175c03?context=repo |
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
1 participant
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.
fix: #66
resolve: #68
Check and return error from commit message function.