Pull Upstream
Trigger a sync from the configured upstream for the repository in the JWT repo claim. This only works for repositories that were created with an upstream base_repo.
JWT claims
Required scopes: git:write
Requires per repo scope: Yes
Authorizations
JWT bearer token signed with your organization's registered signing key. There is no OAuth authorization server; you mint tokens yourself and the token's scopes claim carries the granted permission scopes. Public scopes: git:read (read repository contents), git:write (write branches, commits, tags, and notes), repo:write (create and manage repositories), org:read (list an organization's repositories). Each operation's security requirement names the scopes it requires. See https://code.storage/docs/getting-started/authentication for how to mint tokens.
Path Parameters
Repository name. Names that contain / or any other character that is not safe in a URL path segment must be URL encoded so the value occupies a single path segment. For example pierre/example is sent as pierre%2Fexample. Plain names such as example can be sent as-is. The server URL-decodes the value before resolving the repository.
Body
Optional sync hints. Most callers can omit the body entirely and simply trigger the next upstream pull.
Optional parameters for triggering a sync from the configured upstream.
Response
Sync trigger accepted. The repository sync runs asynchronously.
Acknowledgement that an upstream sync has been initiated; the sync itself runs asynchronously.
Human-readable status message.
"Repository sync initiated successfully"