A short intro post: the gap between "the YAML looks fine" and "which scenarios can actually run," worked through one example (a deploy reachable with skip_tests=true while tests is skipped). Walks through npx ciproof@0.1.0 check, reading REFUTED / NO VIOLATION FOUND / UNKNOWN, and the GitHub Action. Ends with the honest limits (bounded model; UNKNOWN is not a pass; corpus-specific validation) and an invitation to report false counterexamples. Links: repo, Marketplace, supported-semantics, validation study.
Abishek Giri
Posted on
Your GitHub Actions workflow says one thing. Its execution paths say another.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (1)
Marketplace: github.com/marketplace/actions/cip...