Skip to content

Stale Issues Policy #634

Stale Issues Policy

Stale Issues Policy #634

Triggered via schedule September 20, 2024 01:09
Status Success
Total duration 27s
Artifacts

stale-issues.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
stale
[#751] Error when adding a label: Resource not accessible by integration
stale
[#750] Error when adding a label: Resource not accessible by integration
stale
[#749] Error when adding a label: Resource not accessible by integration
stale
[#748] Error when adding a label: Resource not accessible by integration
stale
[#747] Error when adding a label: Resource not accessible by integration
stale
[#746] Error when adding a label: Resource not accessible by integration
stale
[#745] Error when adding a label: Resource not accessible by integration
stale
[#744] Error when adding a label: Resource not accessible by integration
stale
[#743] Error when adding a label: Resource not accessible by integration
stale
[#742] Error when adding a label: Resource not accessible by integration
stale
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/stale@6f05e4244c9a0b2ed3401882b05d701dd0a7289b. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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 100