git.repositories.run-shadow-ciRun a shadowed mirror's workflows on a branch's current head now (default: the default branch)
POST /git/api/repositories/{repoId}/mirror/shadow-runIAM ci:StartWorkflowChanges state
Request syntax
POST /git/api/repositories/{repoId}/mirror/shadow-run
{
"branch": "string"
}Path parameters
repoIdRequiredstring
Constraints: uuid
Request body
branchOptionalstring
Default: the default branch
Constraints: 1-255 chars
Response
202 with `commitOid`, the head commit the shadow runs were started on. 409 while shadow CI is off.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
commitOidAlwaysstring
The head commit the shadow runs were started on
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 ci:StartWorkflow 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 run-shadow-ci repoIdcurl -X POST "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/mirror/shadow-run" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_repositories_run-shadow-ci.