What runs on your machines

Where your repositories live, what the platform reads and keeps, and how imports, mirrors, scans and webhooks behave when something fails.

Last updated 18 November 2026View as Markdown

Where repositories live

The Git service is part of the Deutsche Cloud control plane; there is nothing to provision per repository. Git objects are kept in object storage and branches and tags in the platform's database. A single git push, over HTTPS or SSH, may carry up to 2 GiB; a larger one is refused (Push exceeds the 2147483648 byte limit over HTTPS). An import is fetched by the platform and has no such request-size limit.

What the platform reads and keeps

What What happens
Pushed files Checked for known credential formats as they arrive. A found secret is never stored: only a redacted preview and a fingerprint are kept.
Lockfiles and manifests Matched against the vulnerability database inside Deutsche Cloud. Your dependency list does not leave it.
Code scanning The platform runs no scanner of its own. It stores and shows the SARIF your workflows upload.
Import tokens A token for a one-off import is used and not kept. A mirror's token is stored encrypted, because every sync needs it.
Push mirror tokens Stored encrypted and never shown again.
Webhook secrets Write-only: never returned by the API.
Webhook deliveries For 30 days: the body sent, the response code or connection error, the time taken and the first 4 KiB of the answer.
Release files Served as plain files (application/octet-stream, as an attachment); access is checked on every download.
CODEOWNERS, required checks Read from the target branch, never from the pull request, so a pull request cannot change who reviews it or which checks it needs.

How failures behave

  • Imports answer at once and run in the background; importState ends in succeeded or failed, with the reason.
  • Very large pushes (more than 30 seconds or 500 MB of new text to scan) are let through rather than refused, and are listed on the Secret scanning page as not fully scanned.
  • Push mirrors only fast-forward and never delete on the remote. A branch that moved there on its own is left alone and reported in rejectedRefs.
  • Mirrors (imports that keep following a source) delete branches that the source deleted, and refuse pushes while they mirror.
  • Webhooks are retried with backoff on a 5xx, 408, 429, a timeout (10 seconds) or a connection failure, 5 attempts in all; any other 4xx fails at once, and a redirect is not followed. A URL with a literal private address is refused when saved; a host name that resolves to a private or internal address is refused when delivered.
  • Merge queue builds that fail, conflict or time out remove their pull request, and every build behind it is rebuilt without it. The branch only moves to a commit whose checks passed.
  • Forks are independent copies: deleting the parent leaves the fork.
  • Auto-merge is turned off, rather than run, when the person who enabled it loses git:MergePullRequest.
Did this page help you?