Skip discussions in the issue_lock workflow - #98146
Merged
Merged
Conversation
The `Lock Threads` workflow failed with `Resource not accessible by integration` once the `dessant/lock-threads` v6.0.2 upgrade fixed the token-length validation crash (https://github.com/vercel/next.js/actions/runs/33529115631). The action processes issues, pull requests, and discussions by default, and discussions are handled exclusively through GraphQL (`search(type: DISCUSSION)`, then `lockLockable`). The workflow token only has `issues: write` and `pull-requests: write`, so every discussion call is rejected and the job fails after issues and PRs have already been locked. This change sets `process-only: 'issues, prs'` so the action never touches discussions, which this workflow was never meant to lock. Granting `discussions: write` would also fix the failure, but skipping discussions keeps the token permissions minimal and matches the workflow's original scope. Co-Authored-By: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
Contributor
Tests PassedCommit: 39c9983 |
eps1lon
changed the title
eps1lon
changed the title
issue_lock workflow
eps1lon
marked this pull request as ready for review
September 1, 2026 16:41
timneutkens
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last remaining
Lock Threadsfailures are likely due to missing permissions for discussions whichdessant/lock-threadshandles by default.This disables discussion handling to get the workflow green to start tracking regressions. We can discuss if we want to lock inactive discussions in a follow-up (which would be new behavior this workflow never performed).