Skip to content
Qualia Docs

Versions_ListSourceCommits

GET
/v1/accounts/{account}/datasets/{dataset}/versions/{version}/sourceCommits
 
curl --request GET \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/versions/example/sourceCommits \
  --header 'X-API-Key: <X-API-Key>'

Lists the repository commits a tag pins, ordered by upload, so a version can be traced to the repositories its episodes came from. INVALID_ARGUMENT for head, which pins none.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
account
required
string

The account id.

dataset
required
string

The dataset id.

version
required
string

The version id.

Query Parameters

Section titled “Query Parameters ”
pageSize
integer format: int32

At most this many commits; 0 means 100, the maximum is 500.

pageToken
string

From a previous response’s next_page_token.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

Response for Versions.ListSourceCommits.

object
sourceCommits

One page of commits.

Array<object>

One repository commit a tag pins: where the bytes of the episodes it took from one upload were published (QUA-3048). A tag’s commits never change.

The {source_commit} id is <upload uuid>-<semantic commit uuid>.

object
name

Accounts/{account}/datasets/{dataset}/versions/{version}/sourceCommits/{source_commit}, under the tag’s own name (not stable or a digest prefix).

string
dataset

Accounts/{account}/datasets/{dataset}: the upload the commit published.

string
repoId

The upload’s Git repository, a UUID.

string
gitOid

The Git object id of the commit, lowercase hex.

string
gitHashAlgorithm

The hash the object id is in: “sha1” or “sha256”.

string
publicationGeneration

The publication of refs/heads/main that wrote the commit; counts up from 1 per repository.

string
semanticCommitId

The commit’s identity across hash algorithms, a UUID.

string
nextPageToken

Empty on the last page.

string
totalSize

Commits the tag pins, across every page.

integer format: int32
Example generated
{
  "sourceCommits": [
    {
      "name": "example"
    }
  ],
  "nextPageToken": "example",
  "totalSize": 1
}

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}