repos.gitCredentials.update
Update a stored HTTPS credential for a generic Git upstream.
Scope: repo:write on the repository.
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
The repository name, for example acme/web.
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.
Updated password or access token for the upstream provider.
"glpat_rotated_token"
Username for HTTPS authentication. Optional. With no username, requests to the upstream send the token as the password with the username x-token-auth for Bitbucket and oauth2 for GitLab, and as the username for Gitea, Forgejo, and Codeberg. sr.ht takes no credential over HTTPS: it serves private repositories and pushes only over SSH. An omitted username clears the stored one.
"oauth2"
Response
Credential updated successfully.