Centralized Workflow

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

1. 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.
2. Clone a code repository. Currently, CodeArts Repo supports code cloning from CodeArts Repo to a local computer by using an SSH key and HTTPS.
3. Create a local branch and compile code or create a branch online and compile code.
4. Commit the modified code file to the cache. Currently, Repo supports code commit with Git Bash or Eclipse.
5. Developers create a merge request.
6. Resolve review comments.
7. Committers merge the MR.