Skip to content

workflow: compliance: More than one commit and excluding Kconfig checks #38

workflow: compliance: More than one commit and excluding Kconfig checks

workflow: compliance: More than one commit and excluding Kconfig checks #38

Triggered via pull request March 24, 2026 05:05
@trantanentrantanen
labeled #222
Status Failure
Total duration 5s
Artifacts

backport.yml

on: pull_request_target
Backport
3s
Backport
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Backport
HttpError: Issues has been disabled in this repository.
Backport
Error: Auto-merging .github/workflows/compliance.yml CONFLICT (content): Merge conflict in .github/workflows/compliance.yml error: could not apply ab6490c... workflows: compliance: More than one commit hint: After resolving the conflicts, mark them with hint: "git add/rm <pathspec>", then run hint: "git cherry-pick --continue". hint: You can instead skip this commit with "git cherry-pick --skip". hint: To abort and get back to the state before "git cherry-pick", hint: run "git cherry-pick --abort". hint: Disable this message with "git config set advice.mergeConflict false"
Backport
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: zephyrproject-rtos/action-backport@6b0bae5b575d289305a22ab11a273941b518994c. 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/