fix: grant write permissions to OpenSpec caller workflow - #2
Merged
Conversation
Reusable workflows cannot exceed the caller token's permissions, so the caller must grant issues and pull-requests write explicitly. Without this the run ends in startup_failure.
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
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.
Why
The OpenSpec caller added in the previous PR ends in startup_failure: the reusable validator requests issues and pull-requests write, but the caller token grants none by default.
What Changes
MODIFIED Requirements
Requirement: OpenSpec body validation
The OpenSpec workflow SHALL run to completion on issue and PR events. The caller MUST grant issues: write and pull-requests: write so the validator can label and comment.
(Previously: every run ended in startup_failure because the callee requested permissions the caller did not grant.)
Scenario
GIVEN this fix is merged to the default branch
WHEN an issue is opened or edited with a body missing OpenSpec sections
THEN the OpenSpec run completes, fails the check, applies needs-info, and comments
Verification