Risky Operations on Repositories

Transferring Repository Ownership

Only the repository owner can perform this operation. The new owner can only be another member in the repository.

Click Transfer. In the displayed Transfer Repository Ownership dialog box, select the target member and click OK.

Figure 2 Transfer Repository

Deleting a Repository

Only members who have the permission to delete repositories can perform this operation. To avoid deletion by mistake, you are advised to enable operation protection before deleting a repository. On the Huawei Cloud Management Console, click the username in the upper right corner. In the displayed dialog box, choose Security Settings > Critical Operations > Operation Protection and enable it.

Figure 3 Enabling operation protection

If operation protection is enabled, security verification is required before deleting a repository. You can use Mobile number, Email address, or Virtual MFA device for verification. After the verification is successful, enter DELETE to delete the repository. Once you delete a code repository, all its content will be permanently deleted. This operation cannot be undone. Please exercise caution.

• If no mobile number is bound, click Bind and bind a mobile number on the Security Settings > Basic Information > Mobile Number page.
• If no email address is bound, click Bind and bind an email address on the Security Settings > Basic Information > Email Address page.
• If no virtual MFA device is bound, click Bind and bind a virtual MFA device on the Security Settings > Critical Operations > Virtual MFA Device page.

Renaming a Repository

Only the repository owner can perform this operation. This will invalidate the original path for access and clone. Exercise caution when performing this operation.

Click Rename. In the displayed dialog box, enter a new name and click OK.

Transferring a Repository

The operator must have the permission to delete the repository and create a repository in the target path. This will invalidate the original path for access and clone. Exercise caution when performing this operation.

• Only one repository can be transferred at a time.
• Cross-project transfer will affect the inherited data from the project. The data from the target project is inherited, and that of the original project is removed, including the member, role, and project-level repository settings.
• If forcible inheritance is enabled at the project level or at both the project and repository group levels, the transferred repository will automatically inherit settings from its project or from its project and repository group in sequence. If forcible inheritance is first enabled at the repository level, its original settings will be cleared after the transfer, regardless of whether forcible inheritance is enabled at the project or repository group level.
• After a repository is transferred across different types of projects, the E2E settings will be cleared.
• Cross-project transfer will clear the member group and role settings (such as protected branches and tags).
• After a cross-project transfer, only members of the target project can transfer the repository.
• Added member groups will be cleared after the transfer.
• Members in the review state will be deleted after the transfer.
• After a transfer, modify the repository addresses in dependent services such as Pipeline and Build, etc.
• After a transfer, update the remote record of the local repository to point to the new address.
• Locked repositories cannot be transferred.
• If the repository transfer times out and the page remains stalled for more than 30 minutes, click Reset to transfer the repository again.
• Cross-tenant repository transfer is not supported.

Click Transfer. In the Transfer Repo dialog box, specify Target Project and Target Group, and click OK.