git.repositories.sync-fork

Fast-forward a fork's branch to its parent's

POST /git/api/repositories/{repoId}/sync-forkIAM git:PushRepositoryChanges stateDestructive

Only a fast-forward: a branch with commits of its own is refused (409), nothing is overwritten. Goes through branch protection, CI and webhooks like a push.

Request syntax

POST /git/api/repositories/{repoId}/sync-fork
{
  "branch": "string"
}

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

Request body

  • branchOptional

    string

    The branch to bring up to the parent's branch of the same name; the default branch when absent

    Constraints: 1-255 chars

Response

200 with `ok: true`, `updated` (false when the branch was already level with the parent) and `commitOid`, the commit the branch is at now.

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

Fields of data

  • okAlways

    true

    Always true in a successful answer
  • updatedAlways

    boolean

    The branch moved; false when it was already level with the parent
  • commitOidAlways

    string

    The commit the branch is at now

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:PushRepository 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 repositories sync-fork repoId

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