Skip to content

Close stale issues and PRs #4029

Close stale issues and PRs

Close stale issues and PRs #4029

Triggered via schedule October 25, 2024 08:01
Status Success
Total duration 17s
Artifacts

stale_issues.yml

on: schedule
stale-prs
5s
stale-prs
stale-issues
7s
stale-issues
answered-issues
5s
answered-issues
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 3 warnings
stale-prs
[#7963] Error when adding a label: Resource not accessible by integration
stale-prs
[#7102] Error when adding a label: Resource not accessible by integration
stale-prs
[#6376] Error when adding a label: Resource not accessible by integration
stale-prs
[#2483] Error when adding a label: Resource not accessible by integration
answered-issues
[#7906] Error when updating this pull request: Resource not accessible by integration
answered-issues
[#7893] Error when updating this pull request: Resource not accessible by integration
answered-issues
[#7886] Error when updating this pull request: Resource not accessible by integration
answered-issues
[#7533] Error when updating this pull request: Resource not accessible by integration
stale-prs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/stale@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
answered-issues
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/stale@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
stale-issues
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/stale@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/