Deny Patch

curl --request POST \
  --url https://app.textql.com/v2/patches/{id}/deny \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "expected_git_ref": "<string>"
}
'

{
  "success": true
}

POST

patches

{id}

deny

Deny Patch

curl --request POST \
  --url https://app.textql.com/v2/patches/{id}/deny \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "expected_git_ref": "<string>"
}
'

{
  "success": true
}

The patch author may always deny their own patch; any other caller needs OWNERS write authority on every changed path. The git ref is preserved, so a denied patch can later be reopened with Restore Patch.

Authorizations

Authorization

string

header

required

API key or JWT token

Path Parameters

string

required

Patch ID

Body

application/json

expected_git_ref

string

required

The patch git_ref the caller reviewed; a stale value returns 409.

Response

Patch denied

success

boolean

Approve Patch Restore Patch