Get card
Download
maintainer-approval@1.0.0.yamlClone
npx -y darkprint clone maintainer-approval@1.0.0There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.
Hold the run at the merge boundary until a maintainer with write rights reads the green test report and approves, and emit their verdict as the only thing the merge step will act on.
used in 1 blueprint
Specification
115 words · handed to the agentHold the run here and put the test report you are handed in front of a maintainer who holds write access to this repository. Show them the suite results, the durations and the coverage delta as they were reported, and let them open the drafted review themselves if they want the findings; do not summarise the change for them and do not recommend an outcome. Wait for exactly one such maintainer to approve or reject, there is no timeout, no default verdict and no substitute approver without write access. Emit their verdict and nothing else on approval, and on a rejection emit nothing at all, so the step after you has nothing to act on.
Interfaces
2 in · 1 outInputs
2Outputs
1| Name | Data type | Description |
|---|---|---|
| approval | status | The maintainer's verdict, and nothing else, the merge step reads no other input. |
Dependencies
1The upstream nodes this card expects to receive from. Whenever a blueprint pins this card, each name is checked against a real edge in that graph. A name without a link is not a published card; it refers to a node inside some graph.
Card values
15 declaredWho the node is. The id is the key the DOT pins.
- id
- maintainer-approval
- name
- Maintainer Approval
- type
- human-gate
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action34 words
- Hold the run at the merge boundary until a maintainer with write rights reads the green test report and approves, and emit their verdict as the only thing the merge step will act on.
- spec115 words
- Hold the run here and put the test report you are handed in front of a maintainer who holds write access to this repository. Show them the suite results, the durations and the coverage delta as they were reported, and let them open the drafted review themselves if they want the findings; do not summarise the change for them and do not recommend an outcome. Wait for exactly one such maintainer to approve or reject, there is no timeout, no default verdict and no substitute approver without write access. Emit their verdict and nothing else on
approval, and on a rejection emit nothing at all, so the step after you has nothing to act on.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- not named
- tools
- Human review
- mcp
- none
- params
- approver_scope: write-access, required_approvals: 1
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- test_report : report, review : markdown
- outputs
- approval : status
- dependencies
- test-runner
- cannot
- no type is refused
- will_not
- summarise the change for the maintainer, recommend an outcome
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes46 words
reviewis optional because an edge carries a single value: the test runner wires its report, and the maintainer pulls the draft from the PR thread. This gate is the whole point of the blueprint, and thehuman-gatetype is the whole of what says so.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- maintainer-approval@1.0.0currentsha256:4570e4e86036266a4fc69a46157c69660a2753a32d0fc32acc3c45617b368093
pinned byGuarded Merge Bot
autogen/guarded-merge-bot
A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.
First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.
Community notes (0)
No notes yet.
Nobody has posted about this node card yet.
Sign in to post a note.