Dismiss or reopen a secret scanning alert

Dismiss a secret scanning alert (state dismissed, with a reason: false_positive, used_in_tests, revoked or wont_fix, and an optional comment) or reopen it (state open).

PATCH/repos/{owner}/{name}/secret-scanning/alerts/{id}

Revoked marks it fixed; the others let pushes carrying it through. Takes the Write role, or a security manager of the workspace.

Takes the Admin role: a dismissed secret is let through push protection, unless it was revoked, which marks it fixed. state open reopens it.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: security with action update_secret_alert, and the same inputs
Scope: An access token needs security:write.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.
`id`	string	Yes	The alert’s id: sec_…

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`state`	string	Yes	dismissed, with a reason, or open to reopen. One of `open`, `dismissed`.
`reason`	string	No	Why it is dismissed. revoked marks it fixed. One of `false_positive`, `used_in_tests`, `revoked`, `wont_fix`.
`comment`	string	No	Why, in a sentence; kept with the alert. At most 500 characters.

Example request

curl -X PATCH https://api.g1t.sh/repos/flagon-io/hello/secret-scanning/alerts/sec_01kq2m7d4e5f6g7h8j9k0m1n2p \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "dismissed",
    "reason": "revoked",
    "comment": "Rotated in the issuer'\''s settings."
  }'

Example response

A successful request answers 200 with:

{
  "id": "sec_01kq2m7d4e5f6g7h8j9k0m1n2p",
  "repo_id": "rep_01kp0a1b2c3d4e5f6g7h8j9k0m",
  "kind": "github_token",
  "label": "a GitHub token",
  "path": "scripts/release.sh",
  "line": 12,
  "commit": "4807077b296e6edbf410d55e72749d3e1170c291",
  "preview": "ghp_X7…",
  "status": "resolved",
  "source": "push",
  "found_by": "syntaqx",
  "found_at": "2026-10-06T09:14:02.118Z",
  "decided_by": "syntaqx",
  "reason": "Rotated in the issuer's settings.",
  "decided_at": "2026-10-06T09:20:41.502Z",
  "dismissed_reason": "revoked",
  "test_value": null,
  "state": "fixed",
  "validity": "active",
  "validity_checked_at": "2026-10-06T09:20:41.502Z",
  "bypass": {
    "reason": "will_fix_later",
    "comment": "Rotating it this afternoon.",
    "by": "syntaqx",
    "at": "2026-10-06T09:14:02.118Z",
    "approved_by": null
  },
  "pattern_id": null,
  "pattern_name": null,
  "locations": 1
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.