Repository navigation
fix(super-linter): use the standard conventional commit policy - #282
Merged
Merged
Conversation
Contributor
|
Hi, thank you for creating your PR, we will check it out very soon |
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Contributor
Built Images Summary
Image Detailssuper-linterPull command: Full image references:
Annotations:
|
Contributor
|
Code Coverage Report - super-linter Test Results - super-linterTest Results
|
This was referenced Nov 7, 2026
Merged
Merged
Merged
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
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.
The shared Super-Linter fallback duplicates only part of commitlint's Conventional Commits preset and omits its parser. Consequently valid breaking-change headers such as
feat!: change release inputsfail withtype-emptyandsubject-empty, while body-length checks differ from repositories using the upstream preset.Use the installed
@commitlint/config-conventionalpreset directly, without rule overrides or bot exemptions. Keep existing project/global configuration precedence for consumers that explicitly configure commitlint. Document the policy and give Dependabot explicit conventional message prefixes.Validation: built the image and passed 21 focused testcontainers cases, including breaking-change parsing, strict bot/contributor checks, configuration precedence, and the real Super-Linter commit-history integration test. Biome, Markdown formatting and ShellCheck passed.
This is the image foundation for the shared commit-process rollout. Consumer PRs will use its CI-built image by immutable digest for evaluation and must switch to a released image before merging.