This repository was archived by the owner on May 5, 2024. It is now read-only.
[automatic-releases] Do not drop commits without known type #27
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.
Projects may have different conventions that those mandated by the
conventional-commits-parser[1] package. For example, it is customary
to also prefix commits depending on the area of change such as
src: fix foobar
tests: Fix another test
All these commits, when they are parsed, they end up with type == "src"
or type == "tests" and the package was dropping them silently because
they did not have a known type. However, we shouldn't do that but we
should let projects be flexible on how they use their commit messages
and simply list them along with those of type == null if they do not have a
known type.
[1] https://www.npmjs.com/package/conventional-commits-parser