Module branch 

speccoder attest verify --branch (and attest badge): every ticked task of the units a branch touches, mapped to the commit that carries its evidence and checked with attest verify’s own rules (super::verify::object), plus what only a branch can show: a tick with no evidence at all, a task line edited after its tick, a cited requirement changed since, a commit a squash merge lost.

Everything is read from git objects of the repository at the given head, never from a working tree, and trust comes only from the caller: a key the branch itself declares is never trusted.

Structs

Checked

A finished check: the report and where it was read from.

Options

What a branch check is asked.

Outputs

Where attest verify --branch writes the check besides its result.

Published

A published check: the result and the workflow-command lines to print.

Refusal

A check that could not start.

Enums

AllowedSigners

Where the verifier’s SSH trust comes from.

Constants

NO_TRUST

The refusal when the caller gave no trust.

Functions

badge

attest badge: the share of ticks with verifying evidence over every unit, as an SVG and a shields.io endpoint. A measurement: ok whenever it was written, whatever the share.

check

Checks the ticks of the units the branch touches.

closed

The tasks of feature closed on head: ticked there, with the commit reachable from it that carries the task’s verdict — (task, commit). What pr publishes held-out sets for; read as recorded, no trust.

locate

One task of feature at the head, for its tour: checked with the caller’s trust when given, else read as recorded (signatures not checked, said in its detail). The report holds that tick alone, or none.

recorded

Every tick of feature at head, read as recorded (no trust, no signature checked): what pr’s body tours show before a maintainer’s verifier checks them.

result

The report as a command result.

verify

attest verify --branch for the repository containing start, as a command result named command (payload branch_verify).

verify_and_publish

verify, and the check written where out asks. A file that cannot be written makes the result an error (the report stays its payload).