Skip to main content
POST
Create Tag

Authorizations

Authorization
string
header
required

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

repo_name
string
required

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

application/json

Create a lightweight tag that points to an exact commit SHA.

Create-tag request body describing the new tag and the commit it points to.

name
string
required

Tag name. Must be a valid Git ref name and must not start with refs/.

Example:

"v1.0.0"

ref
string

Branch, tag, or commit the tag should point to. Provide ref or the deprecated target.

Example:

"main"

target
string
deprecated

Deprecated: use ref. Commit the tag should point to.

Example:

"a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2"

Response

Tag creation result.

Result of creating a tag.

message
string
required

Human-readable result message.

Example:

"tag created"

name
string
required

Tag name.

Example:

"v1.0.0"

sha
string
required

Commit SHA the tag points to.

Example:

"a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2"