Skip to content

Derive the commits the signature reading is taken at #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iderex merged 1 commit into from
Aug 30, 2026
Merged

Derive the commits the signature reading is taken at #228

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions docs/quality-parity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -817,17 +817,39 @@ is smaller and worth stating exactly. The requirement is configured on both
boards and the condition record 0023 makes it effective on has been met. That it
has not cost a landing here is a separate reading and it still holds, because
the commits reaching the default branch carry a signature the platform verifies.
Read at the three most recent non-merge commits:
Read at whatever the three most recent non-merge commits are when the command
runs, so the trio moves with the branch instead of being three names typed into
a document:

```
for c in 45bfe62 2edacce 43b4fae; do
for c in $(git log origin/main --no-merges -3 --format='%H'); do
gh api repos/Flowfin/lab/commits/$c --jq '.commit.verification | "\(.verified) \(.reason)"'
done
true valid
true valid
true valid
```

WHAT STOOD HERE NAMED THREE COMMITS AND CALLED THEM THE THREE MOST RECENT. Read
on 2026-08-30 they were the twelfth, thirteenth and fourteenth:

```
git log origin/main --no-merges --format=%h | grep -n '^45bfe62\|^2edacce\|^43b4fae'
12:45bfe62
13:2edacce
14:43b4fae
```

Each of the three still answers `true valid`, so what stopped reproducing was
the superlative above the paste rather than the output under it, and that is the
half of this class hardest to see: a reader checking the evidence checks the
output, and the output was right. What found it was running the command before
quoting the row back, which is how every earlier repair in this section was
found as well. A command that derives its own subjects cannot go wrong in that
direction, and what a re-run refuses instead is the thing this paragraph is
about, which is a commit reaching the default branch without a signature the
platform verifies.

Three commits are three commits and not a property of every account that may
push here. This board takes experiments from anybody, an unsigned history
refuses the merge rather than the commit, and the repair is rebuilding the
Expand Down
Loading