proposal_decide write
Decide a pending proposal: accept, decline or withdraw. Who may decide is fixed: accept and decline belong to the document's owner, its assignee, or to anyone when the document has no owner; withdraw belongs to the proposal's author. Anyone else is refused with invalid_argument naming the owner. Accepting writes the proposed body as the document's description through issue_update's path and records the proposal on that event; declining and withdrawing change the text not at all. A decision is final: a proposal that is no longer pending is refused.
Arguments
| Name | Type | Description |
|---|---|---|
decision required | string | accept: the owner writes the proposed body as the description. decline: the owner refuses it. withdraw: the author takes it back. Accept and decline belong to the document's owner, or to anyone when it has no owner; withdraw to the author One of accept, decline, withdraw. |
proposal required | string | the proposal's ULID, from issue_get's proposals or proposal_create's reply |
Input schema
Exactly what tools/list serves.
input schema
{
"additionalproperties": false,
"properties": {
"decision": {
"description": "accept: the owner writes the proposed body as the description. decline: the owner refuses it. withdraw: the author takes it back. Accept and decline belong to the document's owner, or to anyone when it has no owner; withdraw to the author",
"enum": [
"accept",
"decline",
"withdraw"
],
"type": "string"
},
"proposal": {
"description": "the proposal's ULID, from issue_get's proposals or proposal_create's reply",
"type": "string"
}
},
"required": [
"proposal",
"decision"
],
"type": "object"
}