Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

Stale issues

Stale issues #605

Triggered via schedule December 3, 2023 00:04
Status Success
Total duration 17s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

stale-issues.yaml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
stale
[#204] Error when creating a comment: Resource not accessible by integration
stale
[#204] Error when adding a label: Resource not accessible by integration
stale
[#203] Error when creating a comment: Resource not accessible by integration
stale
[#203] Error when adding a label: Resource not accessible by integration
stale
[#202] Error when creating a comment: Resource not accessible by integration
stale
[#202] Error when adding a label: Resource not accessible by integration
stale
[#201] Error when creating a comment: Resource not accessible by integration
stale
[#201] Error when adding a label: Resource not accessible by integration
stale
[#200] Error when creating a comment: Resource not accessible by integration
stale
[#200] Error when adding a label: Resource not accessible by integration
stale
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/stale@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
stale
No more operations left! Exiting...
stale
If you think that not enough issues were processed you could try to increase the quantity related to the operations-per-run (​https://github.com/actions/stale#operations-per-run​) option which is currently set to 30