Open claudioandre-br opened 1 week ago
Hi!
This is expected because we 7.1.0 doesn't include commitlint, and we didn't release 7.2.0 yet.
But you have a point about documentation. It might be helpful to mention that.
Probably a better solution: you guys should run commitlint
with the -g "$LINTER_RULES_PATH"
option.
-g, --config path to the config file; result code 9 if config is missing
Is there an existing issue for this?
Are you using the latest Super-linter version available?
[X] I am using the latest Super-linter version.
[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)
[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.
Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?
Current Behavior
The Docker "slim" image of super-linter includes
commitlint
[1], as expected. So, this works:But the standard image does not. So the below fails silently:
GIT_COMMITLINT is not executed for the command above. No errors, no hints, nothing.
This also works (this looks "slim", e.g., no
goreleaser
banner):[1] [GIT_COMMITLINT] commitlint: @commitlint/cli@19.5.0
Expected Behavior
standard
:super-linter/super-linter@[VERSION]
: includes all supported linters.All means ALL.
Super-Linter version
Super-linter configuration
Relevant log output
Steps To Reproduce
Run this command and try to find any reference of
commitlint
.Anything else?
BTW:
LINTER_RULES_PATH
variable. This is confusing and undocumented.devel
ortesting
?