Close/Lock issues after inactivity #1195
facebook-github-botneeds-reply.yml
on: schedule
close-issues-needs-more-info
4s
lock-issues-after-closed
4s
Annotations
1 error and 4 warnings
|
lock-issues-after-closed
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID A101:22C292:3E5044C:5EAC73F:6611E6CC.
|
|
lock-issues-after-closed
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: dessant/lock-threads@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
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/
|
|
close-issues-needs-more-info
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/github-script@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
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/
|