Skip to content

Handle stale issues/PRs #312

Handle stale issues/PRs

Handle stale issues/PRs #312

Triggered via schedule April 30, 2024 03:05
Status Success
Total duration 2m 28s
Artifacts

stale.yml

on: schedule
stale
2m 18s
stale
stale-good-first-issues
6s
stale-good-first-issues
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 2 warnings
stale-good-first-issues
[#3038] Error when creating a comment: Resource not accessible by integration
stale-good-first-issues
[#3038] Error when adding a label: Resource not accessible by integration
stale-good-first-issues
[#2698] Error when creating a comment: Resource not accessible by integration
stale-good-first-issues
[#2698] Error when adding a label: Resource not accessible by integration
stale-good-first-issues
[#1879] Error when creating a comment: Resource not accessible by integration
stale-good-first-issues
[#1879] Error when adding a label: Resource not accessible by integration
stale
[#3045] Error when creating a comment: Resource not accessible by integration
stale
[#3045] Error when adding a label: Resource not accessible by integration
stale
[#3024] Error when creating a comment: Resource not accessible by integration
stale
[#3024] Error when adding a label: Resource not accessible by integration
stale
[#2963] Error when creating a comment: Resource not accessible by integration
stale
[#2963] Error when adding a label: Resource not accessible by integration
stale
[#2956] Error when creating a comment: Resource not accessible by integration
stale
[#2956] Error when adding a label: Resource not accessible by integration
stale
[#2947] Error when creating a comment: Resource not accessible by integration
stale
[#2947] Error when adding a label: Resource not accessible by integration
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