Skip to content

chore: enforce OpenSpec format on issues and PRs - #1

Merged
jamubc merged 1 commit into
masterfrom
chore/openspec-validation
Jun 12, 2026
Merged

chore: enforce OpenSpec format on issues and PRs#1
jamubc merged 1 commit into
masterfrom
chore/openspec-validation

Conversation

@jamubc

@jamubc jamubc commented Jun 12, 2026

Copy link
Copy Markdown

Why

Issues and PRs across Jam-Sw follow the OpenSpec format, but this repository does not yet validate bodies, so malformed submissions land unflagged and reviewers discover missing sections by hand.

What Changes

  • Add .github/workflows/validate.yml, the two-line caller for the org-wide reusable OpenSpec validator in Jam-Sw/.github

MODIFIED Requirements

Requirement: OpenSpec body validation

Issues and pull requests in this repository SHALL be checked for the required OpenSpec sections (Why, What Changes, MODIFIED Requirements, GIVEN/WHEN/THEN scenario, numbered Verification) when opened or edited. Bodies missing sections MUST receive a needs-info label and a comment listing what is missing, and the check MUST fail until the body is corrected. Once corrected, the label MUST be removed automatically.
(Previously: no validation ran; malformed issues and PRs were accepted silently.)

Scenario

GIVEN this workflow is merged to the default branch
WHEN an issue is opened with a body missing the Verification section
THEN the OpenSpec check fails, the issue is labeled needs-info, and a comment lists the missing section

Verification

  • 1.1 Open a test issue missing a section and confirm the check fails with the needs-info label and an explanatory comment
  • 1.2 Edit the issue to include all sections and confirm the check passes and the label is removed

Call the org-wide reusable validator so bodies missing OpenSpec sections get a needs-info label, an explanatory comment, and a failing check.
@jamubc
jamubc merged commit 9c27161 into master Jun 12, 2026
@jamubc
jamubc deleted the chore/openspec-validation branch June 12, 2026 15:45
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