Repository navigation
Sift Action v2.0.0 — runs the Sift 1.10.6 engine.
Sift severity now means one thing: Critical — your build failed, and this is why; High — your run is green, but your logs
show something worth noting. A row's severity no longer depends on how large the log is or which internal channel found it,
and on green-to-green pull requests Sift never shows Critical.
The job log is now passed as the exact bytes GitHub serves; each stored baseline records how its bytes were delivered, so
every baseline lineage takes one cold start on upgrade (a warning says so, and the run re-seeds it). Each row is judged
against its own job's declared result; a failed job's row names the step GitHub declares failed; a value in a step's
banner (a commit, a version) no longer splits one step in two.
Breaking inputs (hence v2): the comment levels' significant is now drift; an unknown value for fail-on, pr-comment,
commit-comment or annotations fails the run. @v1 is unchanged; move to @v2 deliberately.
Wording change: one Low row on a job declared successful now reads "declared successful and carrying no declared failure"
where a plain job is named like a sub-job of another (seen once on appwrite).
Known limit: without contents: read, a private repository gets no job graph, so job verdicts and step names stay off.