fix: block completion on any current verifier failure #338

Open
nsaspy wants to merge 0 commits from rage/286-current-verifier-failures into main
Owner

Implements #286 and advances #1.

RED commit c8d3d2624b9ae545e16689804f49c2e5e634c871 proves a current test=passed result can currently mask a current build=failed result. Completion must use latest evidence per verifier kind and fail closed if any current verifier result fails.

Implements #286 and advances #1. RED commit `c8d3d2624b9ae545e16689804f49c2e5e634c871` proves a current `test=passed` result can currently mask a current `build=failed` result. Completion must use latest evidence per verifier kind and fail closed if any current verifier result fails.
Some checks failed
CI / test (pull_request) Failing after 16s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/286-current-verifier-failures:rage/286-current-verifier-failures
git switch rage/286-current-verifier-failures

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/286-current-verifier-failures
git switch rage/286-current-verifier-failures
git rebase main
git switch main
git merge --ff-only rage/286-current-verifier-failures
git switch rage/286-current-verifier-failures
git rebase main
git switch main
git merge --no-ff rage/286-current-verifier-failures
git switch main
git merge --squash rage/286-current-verifier-failures
git switch main
git merge --ff-only rage/286-current-verifier-failures
git switch main
git merge rage/286-current-verifier-failures
git push origin main
Sign in to join this conversation.
No description provided.