Skip to content
Handling stale issues

Handling stale issues #399

Sign in to view logs

Handling stale issues

Handling stale issues #399

Triggered via schedule November 14, 2024 00:16
@gcampbell-msftgcampbell-msft
⁠ 46aff6c
main
Status Success
Total duration 18s
Artifacts –

stale-issues.yml

on: schedule
stale
9s
stale
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
stale
[#664] Error when creating a comment: Resource not accessible by integration
stale
[#664] Error when adding a label: Resource not accessible by integration
stale
[#593] Error when creating a comment: Resource not accessible by integration
stale
[#593] Error when adding a label: Resource not accessible by integration
stale
[#586] Error when creating a comment: Resource not accessible by integration
stale
[#586] Error when adding a label: Resource not accessible by integration
stale
[#584] Error when creating a comment: Resource not accessible by integration
stale
[#584] Error when adding a label: Resource not accessible by integration
stale
[#546] Error when creating a comment: Resource not accessible by integration
stale
[#546] 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/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
stale
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/