[neilime]

Creating a tag on an existing commit can trigger Super-Linter with an empty commit range. Commitlint then rejects identical --from and --to values, failing CI even when the code validators pass. This occurred on the 5.0.0 tag push in meetup-event-automation.

Extend the existing scheduled/manual-run guard to disable commitlint by default when a push payload contains no commits. Pushes with commits and pull requests retain their existing behavior. Explicit commitlint settings and validator allowlists still take precedence. Regenerate the workflow overview from its metadata using CI Dokumentor.

Validation:

• 13 local scenario checks passed against the actual workflow configuration script, covering empty tag/branch pushes, pushes with commits, missing commit data, scheduled/manual runs, pull requests, merge queues, and validator overrides.
• Scoped make lint passed, including the workflow and generated documentation.
• Workflow YAML parsing and git diff --check passed.

Related upstream issue: super-linter/super-linter#7968

[github-actions]

Super-linter summary

Language	Validation result
BIOME_FORMAT	Pass ✅
BIOME_LINT	Pass ✅
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_COMMITLINT	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
JSCPD	Pass ✅
MARKDOWN	Pass ✅
MARKDOWN_PRETTIER	Pass ✅
NATURAL_LANGUAGE	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅
YAML_PRETTIER	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter
Super-linter revision: 2da136927bd4a73596db63044b504547c62cb854
Super-linter version: 9.0.0