Add support for ignored patterns #264
Annotations
4 errors and 2 warnings
test
The message 1 is invalid:
* The line 3 of the message (line 1 of the body) exceeds the limit of 72 characters. The line contains 103 characters: "There was already logic to ignore merge commits, but it was using a very restricted regular expression.". Please reformat the body so that all the lines fit 72 characters.
The original message was:
Add support for ignored patterns
There was already logic to ignore merge commits, but it was using a very restricted regular expression.
This PR:
- Improve the existing merge commit detection.
- Allow users to disable merge commit detection.
- Allow users to provide custom patterns to ignore
Related issues:
- Closes #110
|
test-allow-one-liners
The message 1 is invalid:
* The line 3 of the message (line 1 of the body) exceeds the limit of 72 characters. The line contains 103 characters: "There was already logic to ignore merge commits, but it was using a very restricted regular expression.". Please reformat the body so that all the lines fit 72 characters.
The original message was:
Add support for ignored patterns
There was already logic to ignore merge commits, but it was using a very restricted regular expression.
This PR:
- Improve the existing merge commit detection.
- Allow users to disable merge commit detection.
- Allow users to provide custom patterns to ignore
Related issues:
- Closes #110
|
build
The message 1 is invalid:
* The subject must start with a capitalized word, but the current first word is: "change". Please capitalize to: "Change".
The original message was:
change SomeClass to OtherClass
SomeClass with OtherClass
|
build
The message 1 is invalid:
* The subject must start with a capitalized word, but the current first word is: "change". Please capitalize to: "Change".
The original message was:
change SomeClass to OtherClass
Do something
The message 2 is invalid:
* The first word of the subject ("Change") must not match the first word of the body. Please make the body more informative by adding more information instead of repeating the subject. For example, start by explaining the problem that this change is intended to solve or what was previously missing (e.g., "Previously, ....").
The original message was:
Change other subject
Change body
|
test
The following actions uses node12 which is deprecated and will be forced to run on node16: ./. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
test-allow-one-liners
The following actions uses node12 which is deprecated and will be forced to run on node16: ./. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|