Research and development management and control method and device based on multiple branches of code resources

Abstract

The invention relates to a research and development management and control method and device based on multiple branches of code resources, and the method comprises the steps: importing the code resources into a code view database, creating a schedule, and obtaining a devolop branch and a release branch corresponding to the schedule based on a master branch; obtaining a feature branch on the basis of the feature branch, detecting the code resource on the feature branch on the basis of a development task, and binding an editing permission and the development task; and after code development and auditing are completed, the feature branch is merged into the develop branch, the develop branch is merged into the release branch, packaging and production are carried out on the basis of the release branch, and the code is edited to the master branch. Based on the Coding code hosting technology, unified control over the code resource editing authority is achieved through operation of code resource detection and revocation detection, code editing authority control under the condition of multi-person multi-branch development is supported, the risk of code coverage is effectively reduced, the code management capacity is enhanced, and the system function commissioning accuracy is guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of code R&D management, and in particular to a R&D management method and device based on multiple branches of code resources. Background Art

[0002] The code hosting platform Coding can provide two common version control tools, Git / SVN, for code collaboration and management. You can set up protected branches, and protected branches can only be updated by designated members to prevent important branches in development from being modified by other members. Currently, existing technologies can create a master branch in a centralized library based on R&D task requests; based on the R&D tasks of the master branch, create multiple independent feature branches in the centralized library, establish a mapping relationship between the R&D tasks on the feature branch and the R&D tasks on the master branch, and clone them to the local library; after the R&D tasks on the feature branch are completed, create a develop branch in the centralized library, merge the feature branch that has completed the R&D task into the develop branch, and clone it to the local library at the same time; after the dev branch passes the self-test, merge this branch into the release branch for production, delete the develop branch after production is completed, and create a tag to mark it.

[0003] Currently, Coding can support the creation of different branches, such as feature branches, development branches, release branches, and master branches to ensure the isolation of code resources. However, Coding does not yet support scenarios where some core functions want to prevent the same resource in the same branch from being edited by multiple people at the same time. In addition, if the merging of resources from a feature branch to a development branch requires approval, Coding does not have a relevant mechanism. Summary of the invention

[0004] In order to address the shortcomings of the prior art, the present invention proposes a method for allocating editing permissions for code resources in a multi-person and multi-branch scenario, supports the management and control of code editing permissions for the same code resource in multiple branches and a single branch, and can provide a code review function. Only code resources that have passed the review can be merged between branches.

[0005] To achieve the above objectives, the technical solutions adopted by the present invention include:

[0006] A R&D management and control method based on multiple branches of code resources, characterized by comprising:

[0007] S1. Import code resources into the code view database, create a schedule, and obtain the develop branch and release branch corresponding to the schedule based on the master branch;

[0008] S2. Acquire a feature branch based on the develop branch, check out the code resource based on the development task in the feature branch, and bind the editing permission to the development task;

[0009] S3. After code development and review are completed, the feature branch is merged into the develop branch, and the develop branch is merged into the release branch. The code is packaged and put into production based on the release branch, and the code is tracked to the master branch.

[0010] Furthermore, the code resources include a list path, a corresponding project, a corresponding module, a code manager, and a code reviewer.

[0011] Furthermore, the feature branch includes a first feature branch, a second feature branch and a third feature branch.

[0012] Furthermore, acquiring a feature branch based on the develop branch, checking out the code resource based on the development task in the feature branch, and binding the editing permission to the development task include:

[0013] Assign a first development task, and obtain a first feature branch based on the develop branch; assign a second development task, and obtain a second feature branch based on the develop branch; assign a third development task, and obtain a third feature branch based on the develop branch;

[0014] In the first feature branch, the code resource is checked out based on the first development task, and the editing permission is bound to the first development task; in the second feature branch, the code resource is checked out based on the second development task, and the editing permission is bound to the second development task.

[0015] Furthermore, the first development task and the second development task are assigned to the first developer, and the third development task is assigned to the second developer. When the developer checks out the code resource, the editing authority is bound to the developer and the development task. The allocation of editing authority for multiple people and multiple branches includes the following situations:

[0016] When the first developer checks out the code resource based on the first development task in the first feature branch and locks the code resource, the first developer has editing authority in the second feature branch and can check out the code resource based on the second development task;

[0017] When the first developer checks out the code resource based on the first development task in the first feature branch and locks the code resource, the second developer does not have editing authority in the third feature branch and cannot check out the code resource based on the third development task.

[0018] Furthermore, after the code development and review are completed, the feature branch is merged into the develop branch, the develop branch is merged into the release branch, and the code is packaged and put into production based on the release branch, and the code is tracked to the master branch, including:

[0019] After the code development is completed, the code of the first feature branch and the second feature branch is reviewed;

[0020] After the code is reviewed and approved, the first feature branch and the second feature branch are merged into the develop branch;

[0021] Package, publish, deploy, and test the merged development branch;

[0022] After the test passes, the develop branch is merged into the release branch, and the code is packaged and put into production based on the release branch. After production is completed, the code is tracked to the master branch, and the code resources are automatically unchecked to release the locked code resources.

[0023] The present invention also relates to a R&D control device based on multiple branches of code resources, which is characterized by comprising:

[0024] A branch acquisition module is used to import code resources into the code view database, create a schedule, and obtain the develop branch and release branch corresponding to the schedule based on the master branch;

[0025] A permission binding module, used to obtain a feature branch based on the develop branch, check out the code resource based on the development task in the feature branch, and bind the editing permission to the development task;

[0026] The packaging and production module is used to merge the feature branch into the development branch, merge the development branch into the release branch, and package and produce the code based on the release branch after the code development and review are completed, and track the code to the master branch.

[0027] The present invention also relates to a computer-readable storage medium, characterized in that a computer program is stored on the storage medium, and the computer program implements the above method when executed by a processor.

[0028] The present invention also relates to an electronic device, characterized in that it comprises a processor and a memory;

[0029] The memory is used to store program instructions;

[0030] The processor is used to execute the above method by calling program instructions.

[0031] The present invention also relates to a computer program product, comprising a computer program and / or instructions, characterized in that the computer program and / or instructions implement the steps of the above method when executed by a processor.

[0032] The beneficial effects of the present invention are:

[0033] The R&D control method and device based on multi-branch of code resources described in the present invention adopts the Coding-based code hosting technology, realizes the unified control of code resource editing permissions through the operations of code resource checkout and cancellation, and manages code resources in a unified manner through operations such as adding, editing, deleting, and reviewing, supports code resource management in the case of multi-person and multi-branch development, effectively reduces the risk of code coverage, strengthens code management capabilities, and ensures the accuracy of system function production. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0035] Figure 1 A schematic diagram of a process flow of a research and development control method based on multiple branches of code resources of the present invention;

[0036] Figure 2 This is a schematic diagram of the structure of a research and development control device based on multiple branches of code resources according to the present invention;

[0037] Figure 3 The figure is a schematic structural diagram of an electronic device of the present invention. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. It should be understood that the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments, and these embodiments are only used to illustrate the present application and are not used to limit the scope of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0039] like Figure 1 As shown, the embodiment of the present invention discloses a R&D management and control method based on multiple branches of code resources, and the steps of the process include:

[0040] Step S1. Import code resources into the code view database, create a schedule, and obtain the develop branch and release branch corresponding to the schedule based on the master branch.

[0041] In this embodiment, the list path, project, module, code manager, code reviewer and other information of all code resources that need to be managed in the project are imported into the code view database as the basic data of the code view, and a schedule for the specified launch date is created based on the production date, and the corresponding development branch and release branch are pulled based on the master branch.

[0042] Step S2. Acquire a feature branch based on the develop branch, check out the code resource based on the development task in the feature branch, and bind the editing permission to the development task.

[0043] In an embodiment of the present invention, according to the assigned development task, based on the develop branch created based on the schedule, the feature branch corresponding to the development task is pulled, and the developer can check out the specified code resource through the code view management page based on the development task. After the code resource is checked out, its editing permission is bound to the current developer and the development task.

[0044] Specifically, acquiring a feature branch based on the develop branch, checking out the code resource based on the development task in the feature branch, and binding the editing permission to the development task include:

[0045] Assign a first development task, obtain a first feature branch based on the develop branch, assign a second development task, obtain a second feature branch based on the develop branch, assign a third development task, and obtain a third feature branch based on the develop branch;

[0046] In the first feature branch, the code resource is checked out based on the first development task, and the editing permission is bound to the first development task. In the second feature branch, the code resource is checked out based on the second development task, and the editing permission is bound to the second development task.

[0047] In this embodiment, the first development task and the second development task are assigned to the first developer, and the third development task is assigned to the second developer. When the developer checks out the code resource, the editing authority is bound to the developer and the development task. The allocation of editing authority for multiple people and multiple branches includes the following situations:

[0048] When the first developer checks out the code resource based on the first development task in the first feature branch and locks the code resource, the first developer has editing authority in the second feature branch and can check out the code resource based on the second development task;

[0049] When the first developer checks out the code resource based on the first development task in the first feature branch and locks the code resource, the second developer does not have editing authority in the third feature branch and cannot check out the code resource based on the third development task.

[0050] The same code resource cannot be checked out simultaneously between different scheduled branches. Different development task branches of the same developer under the same scheduled branch can repeatedly check out the same code resource. By allowing developers to check out the same resource multiple times in the same schedule, this method can cope with the scenario where defects appear in the code after the first checkout and need to be redeveloped.

[0051] Step S3. After the code development and review are completed, the feature branch is merged into the develop branch, and the develop branch is merged into the release branch. The code is packaged and put into production based on the release branch, and the code is tracked to the master branch.

[0052] After the developer completes the code development work, he / she submits it for review, and conducts code review on the first feature branch and the second feature branch. The reviewer checks whether the modified content is correct. After the review is passed, the code resources are merged from the feature branch to which the development task belongs to the develop branch to which the schedule belongs. In this embodiment, the first feature branch and the second feature branch code are merged into the develop branch. After the merger is completed, the code is built and deployed through the release process, and the develop branch is packaged, released, deployed, and tested. After the test passes, the develop branch is merged into the release branch, and the package is put into production based on the release branch. After the production is completed, the code is tracked to the master branch, and the code resources are automatically unchecked to release the locked code resources.

[0053] like Figure 2 As shown, the embodiment of the present invention discloses a R&D control device based on multiple branches of code resources, and its structure includes:

[0054] A branch acquisition module is used to import code resources into the code view database, create a schedule, and obtain the develop branch and release branch corresponding to the schedule based on the master branch;

[0055] A permission binding module, used to obtain a feature branch based on the develop branch, check out the code resource based on the development task in the feature branch, and bind the editing permission to the development task;

[0056] The packaging and production module is used to merge the feature branch into the development branch, merge the development branch into the release branch, and package and produce the code based on the release branch after the code development and review are completed, and track the code to the master branch.

[0057] By using this device, the above-mentioned calculation processing method can be executed and the corresponding technical effects can be achieved.

[0058] Taking the core banking system as an example, the following uses coding tools and code view functions to conduct R&D management and control based on multiple branches of code resources.

[0059] The first step is to import the code resource A information of the core system into the code view tool, maintain the code resource's project, module, development manager, and code reviewer information in the code view tool, create an online schedule based on the established online plan, and pull the develop branch corresponding to the scheduled online date from the master branch based on the online date corresponding to the schedule. The code stored in the develop branch is the collection of code that has passed the review of this schedule.

[0060] In the second step, development task 1 is assigned to developer 1. Developer 1 pulls feature_1 branch corresponding to development task 1 based on the scheduled develop branch. On this feature_1 branch, developer 1 can check out code resource A that needs to be edited based on development task 1 and carry out development work. The same developer may be assigned multiple development tasks. Development task 2 is assigned to developer 1. Developer 1 pulls feature_2 branch corresponding to development task 2 based on the scheduled develop branch. If development task 1 that previously checked out code resource A has been completed, then on this feature_2 branch, developer 1 can continue to check out code resource A that needs to be coded based on development task 2 and carry out development work; but if development task 3 is assigned to developer 2 at this time, developer 2 pulls feature_3 branch corresponding to development task 3 based on the scheduled develop branch, then developer 2 cannot check out code resource A based on development task 3 because the edit selection of code resource A has been locked by developer 1's development task. This step is the key logic of the code view, which can effectively prevent the same code resource from being edited by multiple people at the same time in the same online schedule, effectively reducing the risk of code coverage, reducing the risk of production, and reducing the probability of production problems.

[0061] In the third step, after the code review is passed, it will be merged into the development branch corresponding to the schedule; the development branch will be built, deployed, released, and tested. During this process, the content that needs to be put into production for the schedule will be fully tested and verified; after the test passes, the development branch will be merged into the release branch, and after being merged into the release branch, it will be repackaged for final regression verification and functional verification. If there are no problems, the release branch will be packaged and the project will be launched on the scheduled production day; after the project is put into production, all checked-out resources corresponding to the schedule will be automatically unchecked, and all locked code resources will be automatically released. The subsequent scheduling will be carried out in a cycle according to this process.

[0062] An embodiment of the present invention also provides a computer-readable storage medium capable of implementing all the steps in the method in the above embodiment, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, all the steps in the method in the above embodiment are implemented.

[0063] The embodiment of the present invention further provides an electronic device for executing the above method, as a device for implementing the method, and its structure is as follows: Figure 3As shown, the electronic device 300 includes: a processor 301 and a memory 303. The processor 301 and the memory 303 are connected, such as through a bus 302. Optionally, the electronic device 300 may also include a transceiver 304. It should be noted that in actual applications, the transceiver 304 is not limited to one. It is understandable that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the specific structure of the electronic device 300. In other embodiments of the present application, the electronic device 300 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. Optionally, the electronic device may also include a display screen 305 for displaying images, or receiving user operation instructions when necessary.

[0064] The processor 301 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 304 may include a receiver and a transmitter. The transceiver 304 is applied in the embodiment of the present application to implement the function of the electronic device of the embodiment of the present application communicating with other devices when executed.

[0065] Processor 301 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 301 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0066] The processor 301 may also include one or more processing units, for example, the processor 301 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processor (NPU). Among them, different processing units may be independent devices or integrated into one or more processors. Among them, the controller may be the nerve center and command center of the electronic device 300. The controller may generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions. A memory may also be set in the processor 301 for storing instructions and data. In some embodiments, the memory in the processor 301 is a high-speed cache memory. The memory may store instructions or data that the processor 301 has just used or circulated. If the processor 301 needs to use the instruction or data again, it may be directly called from the memory. Repeated access is avoided, the waiting time of the processor 301 is reduced, and the efficiency of the system is improved.

[0067] The processor 301 can run the method provided in the embodiment of the present application. The processor 301 can include different devices. For example, when a CPU and a GPU are integrated, the CPU and the GPU can cooperate to execute the method provided in the embodiment of the present application, for example, part of the algorithm in the method is executed by the CPU, and another part of the algorithm is executed by the GPU to obtain faster processing efficiency.

[0068] The bus 302 may include a path to transmit information between the above components. The bus 302 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 302 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0069] The memory 303 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or may include a high-speed random access memory, or may include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0070] Optionally, the memory 303 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 301. The processor 301 is used to execute the application code stored in the memory 303 to implement the method provided in any embodiment of the present application.

[0071] The memory 303 can be used to store computer executable program codes, which include instructions. The processor 301 executes various functional applications and data processing of the electronic device 300 by running the instructions stored in the memory 303. The memory 303 may include a program storage area and a data storage area. Among them, the program storage area may store the code of the operating system, application program, etc. The data storage area may store data created during the use of the electronic device 300 (such as images, videos, etc. collected by the camera application), etc.

[0072] The memory 303 may also store one or more computer programs corresponding to the method provided in the embodiment of the present application. The one or more computer programs are stored in the above-mentioned memory 303 and are configured to be executed by the one or more processors 301. The one or more computer programs include instructions, and the above-mentioned instructions can be used to execute each step in the above-mentioned corresponding embodiment.

[0073] Of course, the code of the method provided in the embodiment of the present application can also be stored in an external memory. In this case, the processor 301 can run the code of the method stored in the external memory through the external memory interface, and the processor 301 can control the running process.

[0074] The display screen 305 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 300 may include 1 or N display screens 305, where N is a positive integer greater than 1. The display screen 305 can be used to display information input by a user or information provided to a user and various graphical user interfaces (GUI). For example, the display screen 305 can display photos, videos, web pages, or files.

[0075] The electronic device provided in the embodiment of the present application is applicable to any embodiment of the above method. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, which will not be repeated here.

[0076] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0077] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A system that specifies the functions of a box or multiple boxes.

[0078] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction system, which is implemented in the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0079] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps of the functions specified in a box or multiple boxes. Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they know the basic creative concept. Therefore, the attached claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0080] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A R&D management and control method based on multiple branches of code resources, characterized in that: include: S1. Import code resources into the code view database, create a schedule, and obtain the develop branch and release branch corresponding to the schedule based on the master branch; S2. Acquire a feature branch based on the develop branch, check out the code resource based on the development task in the feature branch, and bind the editing permission to the development task; S3. After code development and review are completed, the feature branch is merged into the develop branch, and the develop branch is merged into the release branch. The code is packaged and put into production based on the release branch, and the code is tracked to the master branch.

2. The method according to claim 1, characterized in that The code resources include the list path, the project to which it belongs, the module to which it belongs, the code manager, and the code reviewer.

3. The method according to claim 1, characterized in that The feature branches include a first feature branch, a second feature branch and a third feature branch.

4. The method according to claim 3, characterized in that The acquiring of the feature branch based on the develop branch, checking out the code resource based on the development task in the feature branch, and binding the editing permission to the development task include: Assign a first development task, and obtain a first feature branch based on the develop branch; assign a second development task, and obtain a second feature branch based on the develop branch; assign a third development task, and obtain a third feature branch based on the develop branch; In the first feature branch, the code resource is checked out based on the first development task, and the editing permission is bound to the first development task; in the second feature branch, the code resource is checked out based on the second development task, and the editing permission is bound to the second development task.

5. The method according to claim 4, characterized in that The first development task and the second development task are assigned to the first developer, and the third development task is assigned to the second developer. When the developer checks out the code resource, the editing authority is bound to the developer and the development task. The allocation of editing authority for multiple people and multiple branches includes the following situations: When the first developer checks out the code resource based on the first development task in the first feature branch and locks the code resource, the first developer has editing authority in the second feature branch and can check out the code resource based on the second development task; When the first developer checks out the code resource based on the first development task in the first feature branch and locks the code resource, the second developer does not have editing authority in the third feature branch and cannot check out the code resource based on the third development task.

6. The method according to claim 1, characterized in that After the code development and review is completed, the feature branch is merged into the develop branch, the develop branch is merged into the release branch, and the code is packaged and put into production based on the release branch, and the code is tracked to the master branch, including: After the code development is completed, the code of the first feature branch and the second feature branch is reviewed; After the code is reviewed and approved, the first feature branch and the second feature branch are merged into the develop branch; Package, publish, deploy, and test the merged development branch; After the test passes, the develop branch is merged into the release branch, and the code is packaged and put into production based on the release branch. After production is completed, the code is tracked to the master branch, and the code resources are automatically unchecked to release the locked code resources.

7. A R&D control device based on multiple branches of code resources, characterized in that: include: A branch acquisition module is used to import code resources into the code view database, create a schedule, and obtain the develop branch and release branch corresponding to the schedule based on the master branch; A permission binding module, used to obtain a feature branch based on the develop branch, check out the code resource based on the development task in the feature branch, and bind the editing permission to the development task; The packaging and production module is used to merge the feature branch into the development branch, merge the development branch into the release branch, and package and produce the code based on the release branch after the code development and review are completed, and track the code to the master branch.

8. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: including a processor and a memory; The memory is used to store program instructions; The processor is configured to execute the method according to any one of claims 1 to 6 by calling program instructions.

10. A computer program product comprising a computer program and / or instructions, characterized in that: When the computer program and / or the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images