Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- 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
- SSHKey
-
Repository
- Obtain files in the branch directory.
- Obtaining Warehouse Statistics
- Obtains image files of a specific branch in a repository.
- Modifying the Status of a Repository Referenced by a Pipeline
- Checks whether a user has the warehouse administrator permission.
- Sets whether a repository is in public or private state.
- Obtains the content of a specified file in a specified branch of a repository.
- Obtaining the List of Public Sample Templates
- Creating a repository
- Obtain the short ID of the repository based on the repository name and group name to combine the short ID with the URL of the submission details page corresponding to commitid.
- Queries the submission of a branch of a repository based on the group name and repository name.
- Querying the Branch of a Warehouse
- This API is used to query the submission of a branch of a warehouse based on the warehouse ID. More optional parameters are provided.
- Adding a Deployment Key
- Deleting a Repository Deployment Key
- Obtains the last submission statistics of the warehouse.
- Repository Statistics
- Delete repositories
- Check the repository creation status.
- Querying the Tag List of a Warehouse
- Adding a Tag
- Querying the Details of a Warehouse
- Obtains the number of submitted code lines.
- Download Repository
- Creating a Protection Branch
- Obtaining the Repository Branch List
- Obtaining the List of Warehouse Combination Requests
- Obtaining Warehouse Combination Request Details
- V2Project
- RepoMember
- Commit
- File
- User
- WebHook
- Project
- V2 Warehouse Management
- Discussion
- Application Examples
- Appendix
- Videos
- General Reference
On this page
Copied.
Centralized Workflow
Centralized workflows are suitable for small teams that have just transformed from SVN to Git. Centralized workflows are developed in a central repo. Developers clone the repository from the central repo and push the code to the central repo after the development.
Advantages
- Central management. In a centralized workflow, all code repositories are stored in a central repository, facilitating code management and maintenance.
- Efficient collaboration. Team members can share and collaborate with each other through the central repository.
- Secure and reliable. The central repository can be backed up and restored for code security and reliability.
Disadvantages
- Dependency on the central repo: All code depends on the central repo. If the central repo is faulty, the development work of the entire team will be affected.
- Code conflicts: All code is managed in the central repository. Conflicts may occur when team members modify code. Therefore, you need to manually resolve conflicts to ensure code correctness.
- Permission management: All code is managed in the central repository. Therefore, the permissions of team members need to be managed to ensure code security and reliability.
- Not suitable for large project teams: For large project teams, centralized workflows may make it difficult to manage and maintain the central repository, affecting development efficiency and code quality.
Centralized Workflow Process
- Create a code repository. In CodeArts Repo, you can create a custom repository, create a repository using a template, and fork an existing repository. You can also import a local repository, import a Git repository, or import an SVN repository.
- Clone a code repository. Currently, CodeArts Repo supports code cloning from CodeArts Repo to a local computer by using an SSH key and HTTPS.
- Create a local branch and compile code or create a branch online and compile code.
- Commit the modified code file to the cache. Currently, Repo supports code commit with Git Bash or Eclipse.
- Developers create a merge request.
- Resolve review comments.
- Committers merge the MR.
Parent topic: Developing a Workflow
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