Skip to content

Stale Issues Policy #398

Stale Issues Policy

Stale Issues Policy #398

Triggered via schedule January 28, 2024 00:56
Status Success
Total duration 45s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

stale-issues.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
stale
[#438] Error when adding a label: Resource not accessible by integration
stale
[#437] Error when adding a label: Resource not accessible by integration
stale
[#436] Error when adding a label: Resource not accessible by integration
stale
[#435] Error when adding a label: Resource not accessible by integration
stale
[#434] Error when adding a label: Resource not accessible by integration
stale
[#433] Error when adding a label: Resource not accessible by integration
stale
[#432] Error when adding a label: Resource not accessible by integration
stale
[#431] Error when adding a label: Resource not accessible by integration
stale
[#430] Error when adding a label: Resource not accessible by integration
stale
[#429] Error when adding a label: Resource not accessible by integration
stale
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/stale@6f05e4244c9a0b2ed3401882b05d701dd0a7289b. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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