fix: latest verifier result governs task completion #341

Open
nsaspy wants to merge 0 commits from rage/280-latest-verifier-result into main
Owner

Implements #280 and advances #1.

RED commit 7763d33a574a53f75d332b459269bc40d7c05238 proves an earlier passing verifier result can currently false-green completion after a later failure for the same verifier kind. The fix will preserve bounded historical evidence while making the latest result authoritative.

Implements #280 and advances #1. RED commit `7763d33a574a53f75d332b459269bc40d7c05238` proves an earlier passing verifier result can currently false-green completion after a later failure for the same verifier kind. The fix will preserve bounded historical evidence while making the latest result authoritative.
Some checks failed
CI / test (pull_request) Failing after 17s
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/280-latest-verifier-result:rage/280-latest-verifier-result
git switch rage/280-latest-verifier-result

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/280-latest-verifier-result
git switch rage/280-latest-verifier-result
git rebase main
git switch main
git merge --ff-only rage/280-latest-verifier-result
git switch rage/280-latest-verifier-result
git rebase main
git switch main
git merge --no-ff rage/280-latest-verifier-result
git switch main
git merge --squash rage/280-latest-verifier-result
git switch main
git merge --ff-only rage/280-latest-verifier-result
git switch main
git merge rage/280-latest-verifier-result
git push origin main
Sign in to join this conversation.
No description provided.