Skip to content
Treaty

dev.superpipeline.check.override.v2

A workspace owner or admin overriding a check from chat: the board, card and check name, a non-blank comment of at most 8192 UTF-8 bytes, and an m.reference to the checks.waiting card. Readers ignore properties they do not know.

How it rides

Section titled “How it rides”

An m.room.message whose content carries suite_event_type: "dev.superpipeline.check.override.v2".

Who sends it, who reads it

Section titled “Who sends it, who reads it”

The carrier is whichever service carries the board’s chat: AgentPod’s hub, or SuperExchange for a board that has moved to it.

Fields

Section titled “Fields”
Field Type Required Description Constraints
msgtype "m.text" no
body string no
schema_version integer yes at least 1
suite_event_type "dev.superpipeline.check.override.v2" yes
board_id string yes at least 1 character; at most 200 characters
card_id string yes at least 1 character; at most 200 characters
check_name string yes pattern ^[^/\s]([^/]*[^/\s])?$; at least 1 character; at most 40 characters
comment string yes pattern \S
m.relates_to object yes
m.relates_to.rel_type "m.reference" yes
m.relates_to.event_id string yes at least 1 character

Example

Section titled “Example”

From fixtures/matrix-events/examples.json, case “checks: an admin overrides a pending verdict with a comment”:

{
  "msgtype": "m.text",
  "body": "Override quality: the grader is down; read it myself",
  "schema_version": 1,
  "suite_event_type": "dev.superpipeline.check.override.v2",
  "board_id": "brd_7c1f",
  "card_id": "crd_8a40",
  "check_name": "quality",
  "comment": "the grader is down; read it myself",
  "m.relates_to": {
    "rel_type": "m.reference",
    "event_id": "$checksWaitingEventId"
  }
}

Refused

Section titled “Refused”

Each of these must fail. The corpus says why:

  • checks: no comment (refused by schema)
  • checks: a blank comment (refused by schema)

Source

Section titled “Source”