CodeArts Repo
CodeArts Repo
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of CodeArts Repo
- Purchasing CodeArts
- Accessing CodeArts Repo Homepage
- Environment and Personal Settings
- Migrating Code and Syncing a Repository
- Creating a Repository
- Viewing Activities
- Viewing Repository Statistics
- Configuring Repository Settings
- Hierarchical Repository Management
- Configuring a Repository
- Managing Repo Member Permissions
- Cloning or Downloading Code Repo to a Local PC
- Uploading Code Files to CodeArts Repo
- Developing a Workflow
- Creating and Configuring a CodeArts Project
- Committing Code to CodeArts Repo and Creating a Merge Request
- Managing Merge Requests
- Managing Code Files
- Security Management
- Best Practices
-
FAQs
- Authentication
- Member Permissions
-
Uploading and Downloading Code
- "Error: Deny by project hooks setting 'default': message of commit" Is Reported When Code Repository Is Pushed from the Local Host to CodeArts Repo
- Pushing Binary Files to CodeArts Repo Failed
- Error "'origin' does not appear to be a git repository..." Is Reported When the Git Push Command Is Executed
- Error "The requested URL returned error: 401" Is Reported When HTTPS Is Used to Clone Code in CentOS
- Error "Merge branch 'master' of https://test.com Please Enter a commit" Is Reported When Pulling Code Using the Git Pull Command
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- How Do I Prevent Files Containing Secrets from Being Pushed to CodeArts Repo?
- Migrating Repositories
- Merge Request
- Fork Sync
- Repository Capacity
- FAQs
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- SSH Key
-
Repository
- Obtaining Files in a Branch Directory
- Obtaining Repository Statistics
- Obtaining Image Files of a Specific Branch in a Repository
- Modifying the Status of a Repository Referenced by a Pipeline
- Checking Whether a User Has the Repository Administrator Permission
- Setting a Repository to Public or Private
- Obtaining the Content of a Specified File in a Specified Branch of a Repository
- Obtaining a Public Template List
- Creating a Repository
- Obtaining a Repository Short ID to Generate the Details Page URL
- Querying a Commit of a Branch by Repository or Repository Group Name
- Querying Branches of a Specified Repository
- Querying a Commit of a Repository Branch by the Repository ID
- Adding a Deploy Key
- Deleting a Deploy Key
- Obtaining the Last Commit Statistics of a Repository
- Repository Statistics
- Deleting a Repository
- Viewing a Repository Creation Status
- Querying the Tag List of a Repository
- Adding a Tag
- Querying Details About a Repository
- Obtaining the number of committed code lines
- Downloading a Repository
- Creating a Protected Branch
- Deleting a Protected Branch
- Deleting Protected Branches in Batches
- Creating a Protected Tag
- Deleting a Protected Tag
- Obtaining a Repository Branch List
- Obtaining the MR List of a Repository
- Obtaining MR Details of a Repository
- Obtaining the Repository IP Address Whitelist
- Adding the Repository IP Address Whitelist
- Modifying the Repository IP Address Whitelist
- Deleting the Repository IP Address Whitelist
- Obtaining the Changes of an MR
- Associating a Repository with a Member Group
- Locking a Repository Based on the Repository Short ID
- Unlocking a Repository Based on the Repository Short ID
- Approving an MR
- Obtaining Associated Work Item Information
- Obtaining Reviewer Information Based on the Repo Short ID and Merge Request Short ID
- Obtaining the List of Changed Files
- Tenant
- Group
- Project (V2)
- RepoMember
- Commit
- File
- User
- Webhook
- Project
- Repository Management (V2)
- Review
- Application Examples
- Appendix
- Videos
- General Reference
On this page
Copied.
What Is CodeArts Repo?
What Is CodeArts Repo?
CodeArts Repo provides software developers with Git-based online code hosting services. It is a cloud code repository that supports security control, member and permission management, branch protection and merging, online editing, and statistics. The service aims to address cross-region collaboration, multi-branch concurrency, code version management, and security issues.
- Code can be read, modified, and committed online at any time from anywhere.
- Online branch management allows efficient concurrent development on multiple branches. You can create, change, and merge branches.
- Protected branches prevent pushes to the branches and prevent the branches from being incorrectly deleted.
- The Domain-level IP address whitelist and data transmissions via HTTPS block unauthorized code downloads to secure data.
- Passwords can be reset.
Why CodeArts Repo?
CodeArts Repo provides efficient and secure code hosting for end-to-end code traceability.
- Innovative full-stack development
- Efficient collaborative code development
- Hierarchical protection
- Code-centered tracing
CodeArts Repo Working Mode
- CodeArts Repo uses GitFlow as the basic working mode.
- Following the rules suggested by GitFlow, small and medium-sized development teams can better manage their development.
- Concurrent development: Features and patches are developed concurrently.
- Teamwork: Developers are aware of the current work of other team members during collaboration.
- Flexibility: Emergency fixes are developed on the hotfix branch.
- Master branch: the most stable branch with complete features and code that can be released at any time.
- Develop branch: a permanent branch with the latest and most complete features. It contains all the code ready for the next release and is used to merge other branches.
- Feature branch: a branch for developing a new feature. Once the development is complete, the feature branch is merged into the develop branch for the next release after passing tests.
- Release branch: a dedicated branch for release preparation.
- Hotfix branch: a branch for fixing bugs in a live production version.
NOTE:
- All feature branches are pulled from the develop branch.
- All hotfix branches are pulled from the master branch.
- All commits to the master branch must have tags to facilitate rollback.
- Any changes that are merged to the master branch must be merged to the develop branch for synchronization.
- The master and develop branches are the main branches and they are unique. Other types of branches can have multiple derived branches.
Feedback
Was this page helpful?
Provide feedbackThank 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.
For any further questions, feel free to contact us through the chatbot.
Chatbot