ci: scope OpenSpec validation to feature changes - #1
Open
jamubc wants to merge 1 commit into
Open
Conversation
Docs, chore, fix, ci, test, refactor, style, build, and perf PRs and issues carry no requirement delta, so they no longer need the OpenSpec proposal sections. The validator now runs its required-section checks only on feature changes (a feat: title or feat/ branch, or an issue labeled feature/enhancement) and clears any stale needs-info label on everything else. Update CONTRIBUTING and the PR template to match.
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
1 participant
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.
Summary
The OpenSpec validation workflow currently demands the full change-proposal format (Why, What Changes, MODIFIED Requirements, SHALL/MUST, GIVEN/WHEN/THEN, numbered Verification) on every PR and issue across the org. That is right for feature work but wrong for docs, chore, and fix changes and for bug reports, which have no requirement delta. They get a red check and a needs-info label with no way to satisfy it honestly. This scopes the format to feature changes only.
Changes
feat:or branchfeat/, or an issue labeledfeature/enhancement). Non-feature targets pass and have any staleneeds-infolabel cleared. The failure comment now states that non-feature changes are exempt.Verification
feat:title, nofeat/branch) passes the OpenSpec checkfeat:PR still fails when it is missing required sections