git.security.update-settings

Turn secret push protection or dependency alerts on or off, set the file size limit

PATCH /git/api/repositories/{repoId}/security/settingsIAM git:UpdateRepositoryChanges stateDestructive

Request syntax

PATCH /git/api/repositories/{repoId}/security/settings
{
  "secretPushProtection": "boolean",
  "dependencyAlerts": "boolean",
  "maxFileSizeMb": "number",
  "autoFix": "enum",
  "autoFixMerge": "boolean"
}

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

Request body

  • secretPushProtectionOptional

    boolean

    Refuse pushes that add a known credential format (on by default)

  • dependencyAlertsOptional

    boolean

    Check lockfiles on the default branch against the vulnerability database

  • maxFileSizeMbOptional

    number

    Largest file a push may add, in MB; null for the platform default of 100

    Constraints: integer, 1-2048

    May be null.

  • autoFixOptional

    enum

    Open a fix pull request automatically: for npm alerts on CISA KEV (exploited), or those and critical ones with a fix (critical). Runs as you; off when you lose access

    One of: off, exploited, critical

  • autoFixMergeOptional

    boolean

    Also merge that pull request automatically once the required checks pass. Needs a protection rule on the default branch that requires status checks; never for a major-version bump

Response

200 with the settings now: secretPushProtection, dependencyAlerts and maxFileSizeMb. Turning dependency alerts on starts a scan.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

  • autoFixAlways

    one of off, exploited, critical

    Which dependency alerts open a fix pull request by themselves: exploited = on CISA KEV, critical = those and critical ones with a fix
  • autoFixMergeAlways

    boolean

    That pull request merges itself once the required checks pass (never a major bump)
  • autoFixDisabledReasonAlways

    string, may be null

    Why the platform turned automatic fixes off (their owner lost access); null otherwise
  • secretPushProtectionAlways

    boolean

    Pushes that add a known credential format are refused
  • dependencyAlertsAlways

    boolean

    The default branch's lockfiles are checked against the vulnerability database
  • maxFileSizeMbAlways

    number, may be null

    Largest file a push may add, in MB; null for the platform default of 100

Checked against the handlers: every route test validates their answers against this schema.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow git:UpdateRepository on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud git security update-settings repoId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_security_update-settings.