Modifying Repository File Contents

This API is used to modify repository file contents.

PUT /v1/{project_id}/git/files/{namespace}/{project}/{path}

Table 1 describes the parameters.

**Table 1** Path parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Tenant's project ID. See Obtaining a Project ID.
namespace	Yes	String	Namespace ID or URL code name. See Obtaining a Repository Namespace.
project	Yes	String	Repository project ID or URL code name. If the value contains a slash (/), replace it with a colon (:). See Obtaining All Projects in a Namespace.
path	Yes	String	File path. If the value contains a slash (/), replace it with a colon (:). See Obtaining a Repository File Directory.

**Table 2** Query parameters
Parameter	Mandatory	Type	Description
ref	Yes	String	Branch name, tag name, or commit SHA value.

**Table 3** Request header parameters
Parameter	Mandatory	Type	Description
Content-Type	Yes	String	Message body type (format). Default value: application/json;charset=utf8.
X-Auth-Token	Yes	String	API calling can be authenticated using a token or AK/SK. If you use a token, this parameter is mandatory and must be set to the token. For details about how to obtain a token, see Obtaining a User Token.
X-Repo-Auth	Yes	String	Authorization name. See Obtaining a Git Repository Authorization List.

**Table 4** Request body parameters
Parameter	Mandatory	Type	Description
message	Yes	String	Description.
content	Yes	String	File content after Base64 encoding.
sha	Yes	String	Blob SHA of a file, which can be obtained through Obtaining Repository File Contents.

**Table 5** Response parameter
Parameter	Type	Description
path	String	File path.

Modify repository file contents.

{
  "message": "update file",
  "content": "IyA9PSBTY2hlbWEgSW5mb3...",
  "sha": "4c294617b60715c1d218e61164a3abd4808a4284cbc30e6728a01ad9aada4481"
}

{
  "path": "app/project.rb"
}

Status Code	Description
200	OK
400	Bad Request

The error code format is SVCSTG.REPO.[Error_ID], for example, SVCSTG.REPO.0401. For details, see ServiceStage Error Codes.

Parent topic: Git Repository Access APIs

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.