ci(labeler): move 'permissions' to the workflow level so labels apply on fork PRs#10766
ci(labeler): move 'permissions' to the workflow level so labels apply on fork PRs#10766sukvvon wants to merge 1 commit into
Conversation
📝 WalkthroughWalkthroughThe PR updates the ChangesGitHub Actions Workflow Permissions Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
|
View your CI Pipeline Execution ↗ for commit e759c42
☁️ Nx Cloud last updated this comment at |
size-limit report 📦
|
🎯 Changes
Move the
permissionsblock from thelabelerjob up to the workflow level (and drop the now-empty workflow-levelpermissions: {}) so theGITHUB_TOKENkeepspull-requests: writeon fork PRs.GitHub Actions caps the token granted to a workflow run from a forked repository to the permissions declared at the workflow level — job-level overrides are ignored in that case. With
permissions: {}at the top, fork PRs received a read-only token andactions/labelerfailed withResource not accessible by integration(see e.g. PR #10765 run).The new shape matches the official
actions/labelerrecommended permissions and the labeler workflow already used inTanStack/router.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit