<aside> <img src="/icons/reorder_gray.svg" alt="/icons/reorder_gray.svg" width="40px" /> Navigation bar | Index - Return
</aside>
<aside> <img src="/icons/reorder_gray.svg" alt="/icons/reorder_gray.svg" width="40px" /> Language：English - 中文
</aside>
This is the Permadao code submission and version control standard, and the code repository is managed using git.
The code repository is managed using branch models, and the main branches are as follows:
The product mainline code maintains a stable codebase for external use, and direct work could not be done on this master branch. Instead, work should be done on other designated, independent feature branches (we will discuss this shortly).**Do not directly submit changes to the master branch.**This is also a common rule in many workflows.
The development branch is the base branch for any new development. When you start a new feature branch, it will be based on the development branch. In addition, this branch also collects all completed features and waits to be integrated into the master branch.
These two branches are referred to as long-lived branches. They will exist throughout the entire lifecycle of the project. Other branches, such as feature branches and release branches, are only temporary. They are created as needed and will be deleted once they have completed their tasks.
Used for feature development, feature characteristics.
