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.

Deprecated: Use /api/repos/{repo_name}/pull-upstream instead.

POST /api/v1/repos/pull-upstream

Pull Upstream

cURL

curl --request POST \
  --url https://api.{cluster}.code.storage/api/v1/repos/pull-upstream \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "ref": "main"
}'

202

{
  "message": "Repository sync initiated successfully"
}

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

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.

after · string

Optional opaque token from a previous pull-upstream response. Reserved for compatibility with future incremental syncs.

ref · string

Optional branch or tag to pull from the configured upstream. Defaults to the repository's tracked default branch.

Example:

"main"

Response

202

application/json

Sync trigger accepted. The repository sync runs asynchronously.

Acknowledgement that an upstream sync has been initiated; the sync itself runs asynchronously.

message · string · required

Human-readable status message.

Example:

"Repository sync initiated successfully"