repos.gitCredentials.create
Create a stored HTTPS credential for a repository configured with 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.
Body
Store HTTPS credentials for a generic Git upstream such as GitLab, Bitbucket, Gitea, Forgejo, Codeberg, or SourceHut.
Request body for storing a new HTTPS Git credential when the repository is identified via the URL path.
Password or access token for the upstream provider.
"glpat_xxxxxxxxxxxx"
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.
"oauth2"
Response
Credential created successfully.