repository

Update a file in a repository if SHA is set, or create the file if SHA is not set

put/repos/{owner}/{repo}/contents/{filepath}

Request

Base URL
https://demo.gitea.com/api/v1
Auth
- HTTP basic
- or API key in query parameter token
- or API key in query parameter access_token
- or API key in header Authorization
- or API key in query parameter sudo
- or API key in header Sudo
- or API key in header X-GITEA-OTP
TypeScript
https://skmtc.dev/gitea/apis/gitea-api/docs/repos/:owner/:repo/contents/:filepath/put.ts
A function with typed inputs. Its response is checked against the schema.

ownerstring required

owner of the repo

repostring required

name of the repo

filepathstring required

path of the file to update

branchstring

branch (optional) is the base branch for the changes. If not supplied, the default branch is used

contentstring required

content must be base64 encoded

force_pushboolean

force_push (optional) will do a force-push if the new branch already exists

from_pathstring

from_path (optional) is the path of the original file which will be moved/renamed to the path in the URL

messagestring

message (optional) is the commit message of the changes. If not supplied, a default message will be used

new_branchstring

new_branch (optional) will make a new branch from base branch for the changes. If not supplied, the changes will be committed to the base branch

shastring

the blob ID (SHA) for the file that already exists to update, or leave it empty to create a new file

signoffboolean

Add a Signed-off-by trailer by the committer at the end of the commit log message.

FileResponse

Oct 28, 20267ef50c4c527f Revision changes
- info
  removed the non-success response with the status
- info
  removed the non-success response with the status
- info
  removed the non-success response with the status
- info
  removed the non-success response with the status
Jul 13, 20264df6be504c96 Revision changes
- info
  added the success response with the status