Skip to content

v0.4.0

Latest

Choose a tag to compare

@guitaripod guitaripod released this 03 Oct 09:47

A passing patch can wait for a person.

  • apply: review on POST /v1/runs (or --review on delegate run/replay) holds a passing patch instead of applying it: the run still ends passed, and its new delivery field reads pending.
  • GET /v1/runs/{id}/patch serves the passing attempt's diff; delegate patch <run> prints it.
  • POST /v1/runs/{id}/apply lands a held patch unstaged after git apply --check, refusing with git's own reason (409) and touching nothing when the tree moved under it; POST /v1/runs/{id}/discard sets it aside. delegate apply|discard <run> do the same from the CLI.
  • Both are recorded on the run as an applied/discarded event after its end and as its delivery (applied, pending, discarded); an existing database gains the column on open.
  • Counts read "1 file" / "2 files", and a run that never passed no longer claims a tier of -.
  • /v1/capabilities lists the review feature.