chore: enforce OpenSpec format on issues and PRs - #1
Merged
Conversation
Call the org-wide reusable validator so bodies missing OpenSpec sections get a needs-info label, an explanatory comment, and a failing check.
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
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
.github/workflows/validate.yml, the two-line caller for the org-wide reusable OpenSpec validator in Jam-Sw/.githubMODIFIED 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-infolabel 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 sectionVerification
needs-infolabel and an explanatory comment