Skip to content

Close/Lock issues after inactivity #1002

Close/Lock issues after inactivity

Close/Lock issues after inactivity #1002

Triggered via schedule September 27, 2023 00:16
Status Success
Total duration 6m 24s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

needs-reply.yml

on: schedule
close-issues-needs-more-info
2s
close-issues-needs-more-info
lock-issues-after-closed
2s
lock-issues-after-closed
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
close-issues-needs-more-info
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lock-issues-after-closed
The following actions uses node12 which is deprecated and will be forced to run on node16: dessant/lock-threads@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lock-issues-after-closed
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/