Skip to content

fix: grant write permissions to OpenSpec caller workflow - #2

Merged
jamubc merged 1 commit into
masterfrom
fix/openspec-permissions
Jun 12, 2026
Merged

fix: grant write permissions to OpenSpec caller workflow#2
jamubc merged 1 commit into
masterfrom
fix/openspec-permissions

Conversation

@jamubc

@jamubc jamubc commented Jun 12, 2026

Copy link
Copy Markdown

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

  • Add a permissions block granting issues and pull-requests write to the caller workflow

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

  • 1.1 Edit an issue missing sections and confirm the run completes with a needs-info label and comment
  • 1.2 Confirm no startup_failure appears in the Actions log

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.
@jamubc
jamubc merged commit c37637b into master Jun 12, 2026
1 check passed
@jamubc
jamubc deleted the fix/openspec-permissions branch June 12, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant