dev.knotless.cancel
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 cancels its runs of the ref or the pull going or waiting for their turn when it reads the request, even those of a workflow whose runs finish, and files their checks as cancelled. A merge queue's batches are not a ref's runs. Naming neither a ref nor a pull asks for nothing. With a workflow, only that workflow's runs are cancelled.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | knotless.dev |
| Indexed |
Record
record · key anyProperties
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
dev.knotless.rerun
recordA repository owner's request that its runners run a ref's or a pull's workflows again.
-
org.tangled.ci.cancelPipeline
procedureCancel running pipeline or specific workflows
-
dev.knotless.queue
recordA pull put in the merge queue of the branch it targets, taken out of it, or turned away by the runner that lands the queue.
-
dev.knotless.autoMerge
recordA pull set to merge by itself once its checks pass, or that setting cancelled.
-
dev.knotless.check
recordWhat a workflow did at a commit a ref pointed at, or at the head of a pull, as the runner that ran it reports.