Skip to content
Treaty

dev.superpipeline.gate.pull_back.v2

A person pulling a held approval back before its release time, as request changes. Needs a non-blank comment of at most 8192 UTF-8 bytes and an m.reference to the gate’s message. 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.gate.pull_back.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.gate.pull_back.v2" yes
gate_id string yes at least 1 character; at most 200 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 “release: a decider pulls back with a comment”:

{
  "msgtype": "m.text",
  "body": "Pulled back: wrong image",
  "schema_version": 1,
  "suite_event_type": "dev.superpipeline.gate.pull_back.v2",
  "gate_id": "gate_6e19",
  "comment": "wrong image",
  "m.relates_to": {
    "rel_type": "m.reference",
    "event_id": "$gateEventId"
  }
}

Refused

Section titled “Refused”

Each of these must fail. The corpus says why:

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

Source

Section titled “Source”