Get card
Download
merge-executor@1.0.0.yamlClone
npx -y darkprint clone merge-executor@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.
Merge the approved head into the base under the configured strategy and emit the resulting commit, refusing to act on anything but a maintainer approval.
used in 1 blueprint
Specification
126 words · handed to the agentYou act on one thing only: the approval signal you are handed. If it is anything other than an approval, stop and emit nothing. On an approval, merge the pull request's head into its base as a single squashed commit whose message is the pull-request title and body, then delete the source branch. If the base has moved and the squash does not apply cleanly, abort, leave the base untouched, leave the source branch in place, and report the conflict instead of resolving it yourself. Emit the resulting commit on merge_commit with its SHA, its parents and the branch it landed on. Use the repository write token scoped to this repository alone, and never push to any ref other than the base branch the approval names.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| approval | status | required | The maintainer's verdict. No approval, no merge, this is the only trigger. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| merge_commit | json | The commit the merge produced, with its parents and the branch it landed on. |
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
18 declaredWho the node is. The id is the key the DOT pins.
- id
- merge-executor
- name
- Merge Executor
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action25 words
- Merge the approved head into the base under the configured strategy and emit the resulting commit, refusing to act on anything but a maintainer approval.
- spec126 words
- You act on one thing only: the approval signal you are handed. If it is anything other than an approval, stop and emit nothing. On an approval, merge the pull request's head into its base as a single squashed commit whose message is the pull-request title and body, then delete the source branch. If the base has moved and the squash does not apply cleanly, abort, leave the base untouched, leave the source branch in place, and report the conflict instead of resolving it yourself. Emit the resulting commit on
merge_commitwith its SHA, its parents and the branch it landed on. Use the repository write token scoped to this repository alone, and never push to any ref other than the base branch the approval names.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/merge-executor.md
- tools
- Git
- mcp
- github
- params
- strategy: squash, delete_source_branch: true
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- approval : status
- outputs
- merge_commit : json
- dependencies
- maintainer-approval
- cannot
- no type is refused
- will_not
- resolve a merge conflict itself, push to any ref other than the base branch the approval names
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- secret-access, unchecked-write
- notes53 words
- This is the node that holds the repo write token, and a token is not something an upstream control node can take away, the human gate in front of it bounds when it fires, not what it could reach. Scope the token to the one repository and the branches you actually merge into.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- merge-executor@1.0.0currentsha256:db7a31f184121807e74e5bcd9904df1c500fbf3f8cc685e21b69a8354579cd48
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.