Get Commit
Resolve a branch name, short SHA, or full SHA to a commit and return the same metadata shape used in commit listings. Use this when you need commit details without computing a diff.
JWT claims
Required scopes: git:read
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.
Query Parameters
Branch name, tag, full commit SHA, short SHA, or other revision Git can resolve. Provide ref or the deprecated sha.
Deprecated: use ref instead. Commit SHA, short SHA, branch name, or other revision Git can resolve.
Response
Commit metadata for the resolved revision.
Commit metadata for a single resolved revision, without diff content.
Resolved commit metadata.