Skip to content

Mark stale issues and pull requests #148

Mark stale issues and pull requests

Mark stale issues and pull requests #148

Triggered via schedule August 25, 2023 02:03
Status Success
Total duration 1m 4s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

stale.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
stale
[#337] Error when creating a comment: Resource not accessible by integration
stale
[#337] Error when adding a label: Resource not accessible by integration
stale
[#335] Error when creating a comment: Resource not accessible by integration
stale
[#335] Error when adding a label: Resource not accessible by integration
stale
[#334] Error when creating a comment: Resource not accessible by integration
stale
[#334] Error when adding a label: Resource not accessible by integration
stale
[#332] Error when creating a comment: Resource not accessible by integration
stale
[#332] Error when adding a label: Resource not accessible by integration
stale
[#331] Error when creating a comment: Resource not accessible by integration
stale
[#331] 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@v3. 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