Repository navigation
fix(linter): skip commitlint by default on scheduled and manual runs - #613
Merged
Merged
Conversation
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
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.
Scheduled and manual runs can give commitlint identical
--fromand--tocommits, causing the lint job to fail withInvalid input flags. This is the failure reported in ci-github-publish run 39280083382 and tracked upstream in super-linter/super-linter#7968.Disable commitlint by default for
scheduleandworkflow_dispatchevents. Preserve explicitlinter-envoverrides and native validator allowlists, and retain the existing defaults for push, pull request, and merge queue events. Document the event-specific behavior.