Skip to content

[REQUEST] Automatic Handling of Nested track calls #366

[REQUEST] Automatic Handling of Nested track calls

[REQUEST] Automatic Handling of Nested track calls #366

Triggered via issue October 30, 2024 03:33
Status Success
Total duration 16s
Artifacts

newissue.yml

on: issues
add-comment
8s
add-comment
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
add-comment
The following actions uses node12 which is deprecated and will be forced to run on node16: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
add-comment
The following actions use a deprecated Node.js version and will be forced to run on node20: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
add-comment
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/