---
url: /en/guide/git-access.md
---
## Git Repository Address

The Git repository address on the Cloud Native Build Platform uses the **repository page address** directly without adding a `.git` suffix. The format is: `https://cnb.build/group-path/repo-path`.

This address is the URL users see when accessing the repository homepage in a web browser, serving as the platform's native access path.

Additionally, the platform supports the traditional format with the `.git` suffix: `https://cnb.build/group-path/repo-path.git`, with both formats providing identical functionality.

### Explanation

* **Design Basis**: The repository page address serves as the usual entry point for users accessing repositories. Using it directly as the Git operation address aligns with user habits, reducing cognitive load.
* **Operational Convenience**: Users can directly copy the repository page address from the browser's address bar (typically a one-click operation) without the need to enter the repository page, click the "Clone" button, and then search for the Git address in a popup window, making operations more direct and efficient.
* **Compatibility**: The format with the `.git` suffix adheres to industry standards, maintaining compatibility for developers accustomed to traditional approaches.
* **Consistent Functionality**: Both formats support full Git operations (such as cloning, pulling, and pushing) without any functional differences.

## Authentication Method

Authentication on this platform is completed via an **access token**, with the specific configuration as follows:

* **Username**: Always enter `cnb`.
* **Password**: Enter the access token you have created (equivalent to a password and supports permission configuration).

For more usage details, please refer to: [Access Token](./access-token.md).

> When connecting with third-party tools (such as IDEs, Git clients), enter the token in the password field and `cnb` in the username field.

### Design Background

* Tokens support fine-grained permission control (e.g., read/write or read-only) and can be revoked or updated at any time in individual settings, offering higher security compared to traditional static passwords.
* Using the fixed username `cnb` simplifies the authentication process, preventing security issues arising from custom username conflicts or weak passwords.

## SSH Not Supported

The Cloud Native Build Platform does not provide support for SSH protocol access, mainly for the following reasons:

1. **Security and Control**: Authentication is accomplished through HTTPS + token, with tokens supporting short-term validity and hierarchical permissions, making them easier to manage than long-term valid SSH private keys and can be revoked at any time.
2. **Enhanced User Experience**: Using the HTTPS protocol with tokens requires no additional configurations (such as generating SSH keys or uploading public keys), reducing barriers for users, especially suitable for beginners and temporary collaborators.
3. **Industry Practices**: Lighter development scenarios (e.g., CI/CD automation) widely adopt the HTTPS + token solution, aligning with technological trends.
