dev.knotless.rerun

Kept in the account of the repository's owner, keyed `<repo key>.<tid>`. A runner acts on the requests in the owner's account, newer than the last it acted on, and on no one else's; it runs the ref or the pull's head where it points when the runner reads it. Naming neither a ref nor a pull asks for nothing. With a ref and a workflow, it runs only that workflow there, its steps seeing env: one that runs on a push to the ref, or one whose trigger is to be asked for. With a pull and a workflow, it runs only that one of the pull's workflows, where the pull is.

Details · record, key any
Kindrecord
Record keyany
Authorityknotless.dev
Indexed

Record

record · key any

Properties

createdAt

requiredstring · datetime

env

array

With workflow, variables its steps see, over the workflow's own of the same names.

  • maxLength: 32
itemsref
Reference

pull

string · at-uri

The dev.knotless.pull record whose head to run again.

ref

string

The full ref name to run again, such as refs/heads/main.

  • maxLength: 1024

repo

requiredref

The repository, which is the owner's.

workflow

string

The name of the one workflow to run at the ref, or of the pull's.

  • maxLength: 64

#var

object

A variable a requested run's steps see.

Properties

name

requiredstring

A shell variable's name, not the runner's own, which begin KNOTLESS_RUN.

  • maxLength: 64

value

requiredstring
  • maxLength: 4096

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Asks a repository's runners to run a ref's or a pull's workflows again, as the owner logged in to this appview's pages.

  • A repository owner's request that its runners cancel the runs of a ref or a pull still going.

  • A repository's workflows at a ref, and what runs each there.

  • What a workflow did at a commit a ref pointed at, or at the head of a pull, as the runner that ran it reports.

  • What a repository's runners ran: every run of its workflows, and the workflows themselves.