You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigated this today while my own PR #214 was tripping both PR Issue Checker and Auto-label on pull_request. It's not just fork PRs - looking at the last runs list, both workflows have been failing repo-wide since at least Dec 2025 (main, opensource-readme, same conclusion).
Root cause for auto-label: actions-ecosystem/action-add-labels@v1 is an old action built for a Node runtime the runners no longer ship, plus the job has no explicit permissions block so label writes depend on the default token config. Since @sanjay-kv asked to keep workflow changes centralized, happy to submit the fix as one small PR if you assign this. The labeler step itself can be replaced with github-script so there is no stale third-party action involved at all:
For pr-checker: the Fixes #<issue> regex itself is fine, but for profile-style PRs (add one name) there is often no issue to fix, so it errors by design on a chunk of incoming PRs. Maybe accept Relates to # / Closes # forms too, or skip the regex for docs-only PRs.
Activity
ziadkix commentedon Nov 6, 2026
Investigated this today while my own PR #214 was tripping both
PR Issue CheckerandAuto-labelon pull_request. It's not just fork PRs - looking at the last runs list, both workflows have been failing repo-wide since at least Dec 2025 (main, opensource-readme, same conclusion).Root cause for auto-label:
actions-ecosystem/action-add-labels@v1is an old action built for a Node runtime the runners no longer ship, plus the job has no explicitpermissionsblock so label writes depend on the default token config. Since @sanjay-kv asked to keep workflow changes centralized, happy to submit the fix as one small PR if you assign this. The labeler step itself can be replaced with github-script so there is no stale third-party action involved at all:For pr-checker: the
Fixes #<issue>regex itself is fine, but for profile-style PRs (add one name) there is often no issue to fix, so it errors by design on a chunk of incoming PRs. Maybe acceptRelates to #/Closes #forms too, or skip the regex for docs-only PRs.