Skip to content

Close/Lock issues after inactivity #846

Close/Lock issues after inactivity

Close/Lock issues after inactivity #846

Triggered via schedule April 23, 2023 00:19
Status Success
Total duration 10s
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
3s
lock-issues-after-closed
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
close-issues-needs-more-info
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/github-script@v3. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
lock-issues-after-closed
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: dessant/lock-threads@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
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/