fix(cli): distinguish validation failure exits - #142
Merged
Conversation
Reserve exit code 2 for invalid repository definitions and records so CI integrations can separate data findings from validator runtime failures. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Give CI consumers repository-relative finding identities and constraint classes without record values. Recover command panics as generic runtime failures so exit code 2 remains reserved for validation findings. Co-Authored-By: OpenAI Codex <noreply@openai.com>
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
Verification
go build ./...go test ./...golangci-lint runwb check . --profile ci(Go lint/test/build passed; SpecScore reported the same 68 repository violations asorigin/main, excluding the temporary baseline checkout's missing-origin-only finding)