Update Git Credential
Update a stored HTTPS credential for a generic Git upstream.
JWT claims
Required scopes: repo: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.
Credential identifier.
Body
Rotate or replace an existing generic Git credential.
Request body for rotating an existing HTTPS Git credential when the credential is identified via the URL path.
Response
Credential updated successfully.