Skip to content

lock

lock #264

Triggered via schedule July 31, 2023 09:02
Status Success
Total duration 11s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

lock.yml

on: schedule
🔒 Lock closed issues and PRs
2s
🔒 Lock closed issues and PRs
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
🔒 Lock closed issues and PRs
The following actions uses node12 which is deprecated and will be forced to run on node16: dessant/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
🔒 Lock closed issues and PRs
Unexpected input(s) 'issue-comment', 'pr-comment', valid inputs are ['github-token', 'issue-lock-inactive-days', 'issue-exclude-created-before', 'issue-exclude-labels', 'issue-lock-labels', 'issue-lock-comment', 'issue-lock-reason', 'pr-lock-inactive-days', 'pr-exclude-created-before', 'pr-exclude-labels', 'pr-lock-labels', 'pr-lock-comment', 'pr-lock-reason', 'process-only']
🔒 Lock closed issues and PRs
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/
🔒 Lock closed issues and PRs
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/