Skip to content

docs: improve config/docs coverage and clarify CLI timeouts #52

docs: improve config/docs coverage and clarify CLI timeouts

docs: improve config/docs coverage and clarify CLI timeouts #52

Re-run triggered March 24, 2026 12:17
Status Failure
Total duration 9s
Artifacts

commit-message-check.yml

on: pull_request
check-subject
4s
check-subject
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
check-subject
Error: Subject line has to contain a commit type, e.g.: "chore: blabla" or a merge commit e.g.: "merge xxx". Valid types are: change - API breaking change feat - API compatible new feature improve - Become better without functional changes perf - Performance improvement dep - dependency update docs - docs update test - test udpate ci - CI workflow update refactor - refactor without function change. fix - fix bug fixdoc - fix doc fixup - minor change: e.g., fix sth mentioned in a review. bumpver - Bump to a new version. chore - Nothing important. build - bot: dependabot.
check-subject
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gsactions/commit-message-checker@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/