Code branch processing method, device, electronic device and storage medium

Abstract

The present application provides a code branch processing method, device, electronic device and storage medium. The method includes: in response to a branch creation trigger instruction, obtaining the requirement information corresponding to the branch creation trigger instruction; the requirement information includes the level identification, object identification and association information of each object to be created, wherein the association information is used to indicate the object that has a superior-subordinate association with the object to be created; according to the source code file and the level identification, object identification and association information of each object to be created, the code branch corresponding to each object to be created is created; the code branch corresponding to each object to be created is stored in the configuration library. The method of the present application can identify the requirement information and automatically create code branches, with a high degree of standardization, reducing the reliance on manual management and control, thereby helping to reduce the uncertainty of branch management strategies in project implementation and improve the development efficiency of the project.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a code branch processing method, device, electronic device and storage medium. Background Art

[0002] In the process of implementing information technology projects, code version management plays a vital role. Project teams usually choose code management tools to manage the code. At the same time, in order to meet the requirements of phased management of the project, the concept of branches is introduced to manage the entire source code by establishing different branches.

[0003] In actual operation, branches are usually created manually. However, due to different understandings of branches among different teams, the branch processing methods vary greatly and the degree of standardization is low, which affects the development efficiency of the project. Summary of the invention

[0004] The present application provides a code branch processing method, device, electronic device and storage medium to solve the problem of low standardization of branch processing affecting project development efficiency.

[0005] In a first aspect, the present application provides a code branch processing method, comprising:

[0006] In response to a branch creation trigger instruction, acquiring requirement information corresponding to the branch creation trigger instruction; the requirement information includes a level identifier, an object identifier, and association information of each object to be created, wherein the association information is used to indicate an object that has a superior-subordinate association with the object to be created;

[0007] Creating a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created;

[0008] The code branches corresponding to the objects to be created are stored in the configuration library.

[0009] In a second aspect, the present application provides a code branch processing device, comprising:

[0010] an acquisition unit, configured to acquire, in response to a branch creation trigger instruction, demand information corresponding to the branch creation trigger instruction; the demand information includes a level identifier, an object identifier, and association information of each object to be created, wherein the association information is used to indicate an object that has a superior-subordinate association with the object to be created;

[0011] A creation unit, used to create a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created;

[0012] The storage unit is used to store the code branches corresponding to each of the objects to be created in the configuration library.

[0013] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect above.

[0014] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect above.

[0015] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method described in the first aspect above.

[0016] The code branch processing method, device, electronic device and storage medium provided in the present application respond to the branch creation trigger instruction, obtain the requirement information corresponding to the branch creation trigger instruction; the requirement information includes the level identification, object identification and association information of each object to be created, wherein the association information is used to indicate the object that has a superior-subordinate association with the object to be created; according to the source code file and the level identification, object identification and association information of each object to be created, create the code branch corresponding to each object to be created; store the code branch corresponding to each object to be created in the configuration library. Accordingly, it is possible to identify the requirement information and automatically create code branches, with a high degree of standardization, reducing reliance on manual management and control, thereby helping to reduce the uncertainty of branch management strategies in project implementation and improve project development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0018] Figure 1 A schematic diagram of a flow chart of a code branch processing method in an exemplary embodiment;

[0019] Figure 2 is a flow chart of a code branch processing method in another exemplary embodiment;

[0020] Figure 3 is a schematic diagram of the structure of a code branch processing device in an exemplary embodiment;

[0021] Figure 4 is a schematic structural diagram of a code branch processing device in another exemplary embodiment;

[0022] Figure 5 is a schematic structural diagram of an electronic device in an exemplary embodiment;

[0023] Figure 6 is a block diagram of an electronic device in an exemplary embodiment.

[0024] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0025] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0026] First, the terms involved in this application are explained:

[0027] Version management: The process of recording, tracking, maintaining and controlling changes in product or system series caused by partial transformation and modification of the same product or system to meet different needs.

[0028] Branch: In the version control process, multiple lines are used to advance multiple tasks at the same time. Each version management timeline is a branch.

[0029] The specific application scenario of this application is the code management system. The project team manages the code through the code management system. At the same time, in order to meet the phased management requirements of the project, the concept of branches is introduced to manage the entire source code by establishing different branches.

[0030] In actual operation, branches are usually created manually. However, due to different understandings of branches among different teams, the branch processing methods vary greatly and the degree of standardization is low, which affects the development efficiency of the project.

[0031] The code branch processing method, device, electronic device and storage medium provided in this application are intended to solve the above technical problems in the prior art.

[0032] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0033] Figure 1 is a flowchart of a code branch processing method according to an exemplary embodiment. Figure 1 As shown, the method includes:

[0034] S101, in response to a branch creation trigger instruction, obtaining requirement information corresponding to the branch creation trigger instruction; the requirement information includes a level identifier, an object identifier and association information of each object to be created, wherein the association information is used to indicate objects that have a superior-subordinate association with the object to be created.

[0035] The execution subject of this embodiment may be a server, a terminal, or a system including a server and a terminal, and there is no limitation on this. This embodiment is described with the execution subject being the server where the code management system is located.

[0036] The branch creation trigger instruction is used to trigger the automatic creation of code branches. Requirement information refers to information produced according to project business requirements, which is used as the basis for automatically creating code branches. Each object to be created in the requirement information corresponds to a code branch to be created.

[0037] Level identifiers are used to distinguish different levels, and each level corresponds to a level identifier. Different levels represent different branch granularities. The higher the level, the coarser the branch granularity, and the lower the level, the finer the branch granularity. The same level can include one or more objects to be created, and object identifiers are used to distinguish different objects to be created.

[0038] For example, the levels include the first level, the second level, the third level and the fourth level in order from coarse to fine branch granularity. A first-level object to be created can be associated with one or more second-level objects to be created, a second-level object to be created can be associated with one or more third-level objects to be created, and a third-level object to be created can be associated with one or more fourth-level objects to be created.

[0039] Exemplarily, the requirement information is itemized requirement information, specifically, a requirement entry table. Optionally, the developer creates a requirement entry table according to the business requirements and the requirement itemization template, and after creating the requirement entry table, sends a branch creation trigger instruction to the server through a client page operation, and the branch creation trigger instruction carries the requirement entry table information. After receiving the branch creation trigger instruction, the server obtains the requirement entry table information carried by the branch creation trigger instruction to create a code branch.

[0040] S102, creating a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created.

[0041] Exemplarily, the server performs a mirror operation on the source code file to obtain a code branch, and each code branch corresponding to the object to be created is a mirror file of the source code file. The server determines the branch identifier corresponding to the object to be created based on the level identifier, object identifier and associated information of the object to be created, so as to identify the code branch corresponding to the object to be created. The branch identifier is used to distinguish different branches, and each code branch corresponds to a branch identifier. At the same time, the branch identifier reflects the associated information, and the branch identifier of the branch can be used to determine the branch that is associated with the branch in the upper and lower levels.

[0042] S103, storing the code branch corresponding to each object to be created in the configuration library.

[0043] After the server obtains the code branch corresponding to each object to be created, it stores the code branch corresponding to each object to be created in the configuration library for deployment, testing, modification and other operations.

[0044] In this embodiment, in response to a branch creation trigger instruction, the requirement information corresponding to the branch creation trigger instruction is obtained; the requirement information includes the level identification, object identification and association information of each object to be created, wherein the association information is used to indicate the object that has a superior-subordinate association with the object to be created; according to the source code file and the level identification, object identification and association information of each object to be created, the code branch corresponding to each object to be created is created; the code branch corresponding to each object to be created is stored in the configuration library. Accordingly, the requirement information can be identified and the code branch can be automatically created, with a high degree of standardization, reducing the reliance on manual management and control, thereby helping to reduce the uncertainty of branch management strategies in project implementation and improving project development efficiency.

[0045] Figure 2 is a flowchart of a code branch processing method according to an exemplary embodiment. Figure 2 As shown, the method includes:

[0046] S201, in response to a branch creation trigger instruction, obtain requirement information corresponding to the branch creation trigger instruction; the requirement information includes a level identifier, an object identifier and association information of each object to be created, wherein the association information is used to indicate objects that have a superior-subordinate association with the object to be created.

[0047] Exemplarily, the implementation of step S201 is similar to that of step S101 and will not be described in detail here.

[0048] S202: Create a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created.

[0049] In one example, based on the source code file and the level identification, object identification and associated information of each object to be created, a code branch corresponding to each object to be created is created, including: based on the level identification of each object to be created, each object to be created is divided into a project object, a milestone object, a requirement object and a function object; based on the source code file and the object identification of the project object, a project branch is created; based on the source code file and the object identification and associated information of the milestone object, a milestone branch is created; based on the source code file and the object identification and associated information of the requirement object, a requirement branch is created; based on the source code file and the object identification and associated information of the requirement object, a function branch is created; wherein, the code branches include project branches, milestone branches, requirement branches and function branches.

[0050] Exemplarily, the levels of the objects to be created include project level, milestone level, requirement level and function level from top to bottom. The requirement information may include a project number, a milestone number, a requirement number and a function number, which serve as object identifiers of project objects, milestone objects, requirement objects and function objects, respectively. A project number may be associated with one or more milestone numbers, a milestone number may be associated with one or more requirement numbers, and a requirement number may be associated with one or more function numbers.

[0051] Exemplarily, the requirement information may further include a project name, a milestone date (production date), requirement content, and a function name.

[0052] The server creates a project branch based on the source code file and the object identifier of the project object, including obtaining the project branch by mirroring the source code file and identifying the project branch based on the project number. The project branch contains project related information such as the project number and project name, and serves as the main branch of the entire project.

[0053] The server creates a milestone branch based on the source code file and the object identifier and associated information of the milestone object, including performing a mirror operation on the source code file to obtain the milestone branch, and identifying the milestone branch based on the milestone number and the project number associated with the milestone number. The milestone branch contains milestone related information such as the milestone number and the production date, which serves as a key node for the project production.

[0054] The server creates a requirement branch based on the source code file and the object identifier and associated information of the requirement object, including obtaining the requirement branch by mirroring the source code file, and identifying the requirement branch based on the requirement number and the milestone number and project number associated with the requirement number. A milestone branch covers a batch of requirements, and the requirement branch contains requirement related information such as the requirement number and the requirement content, which is used as the basis for business acceptance testing.

[0055] The server creates a functional branch based on the object identifier and associated information of the source code file and the functional object, including obtaining the functional branch by mirroring the source code file, and identifying the functional branch based on the functional number and the requirement number, milestone number, and project number associated with the function number. The requirement branch is a mapping of the business function, and the functional branch is the smallest unit of technical implementation. The functional branch contains function-related information such as the function number and function name, and breaks down the functional branch into the smallest unit that can be technically implemented for technical implementation.

[0056] In the above embodiment, by establishing code branches at different levels through the four-layer architecture of "project-milestone-requirement-function", it is possible to realize the automated creation and management of finer-grained branches, starting from the delivery of requirements to the launch of production, which not only takes into account the management of the project implementation stage, but also takes into account the management outside the implementation stage. The development process is associated with the requirements, forming a full-process management and control, realizing complete project life cycle management, which is conducive to improving the standardization of management and control. In addition, the above four-layer architecture can solve the problem of milestone intersection in the project, and manage milestones as the core, which can avoid the series of problems in the common "project-function" model that require code picking or even conflicts due to the adjustment of the production milestone.

[0057] S203, storing the code branch corresponding to each object to be created in the configuration library.

[0058] Exemplarily, the implementation of step S203 is similar to that of step S103 and will not be described in detail here.

[0059] S204, detecting the operation status of each code branch, and if it is detected that the operation status of the code branch meets the merge triggering condition, merging the code branch meeting the merge triggering condition into the upper-level code branch associated therewith.

[0060] A corresponding merge trigger condition can be set for each code branch in advance. The merge trigger condition corresponding to the code branch is used to indicate that when the job status of the code branch meets the merge trigger condition, the code branch is merged. Optionally, the merge trigger condition includes a trigger person, a trigger time, a trigger condition, and a trigger parameter.

[0061] Exemplarily, if it is detected that the job status of the function branch meets the merge trigger condition, the function branch that meets the merge trigger condition is merged into the demand branch associated with it. The merge trigger condition at this time is the merge trigger condition corresponding to the function branch. Optionally, when the integration test of the function branch is completed, the server determines that the job status of the function branch meets the merge trigger condition and merges the function branch into the demand branch associated with it.

[0062] Exemplarily, if it is detected that the job status of the demand branch meets the merge trigger condition, the demand branch that meets the merge trigger condition is merged into the milestone branch associated with it. The merge trigger condition at this time is the merge trigger condition corresponding to the demand branch. Optionally, when the business acceptance corresponding to the demand branch is completed, the server determines that the job status of the demand branch meets the merge trigger condition and merges the demand branch into the milestone branch associated with it.

[0063] Exemplarily, if it is detected that the job status of a milestone branch meets the merge trigger condition, the milestone branch that meets the merge trigger condition is merged into the project branch associated with it. The merge trigger condition at this time is the merge trigger condition corresponding to the milestone branch. Optionally, when the milestone branch is put into production, the server determines that the job status of the milestone branch meets the merge trigger condition and merges the milestone branch into the project branch associated with it.

[0064] Exemplarily, if it is detected that the job status of the project branch meets the merge trigger condition, the project branch that meets the merge trigger condition is merged into the system archive branch associated with it. The merge trigger condition at this time is the merge trigger condition corresponding to the project branch. Optionally, when all milestone branches covered by the project branch are completed, the server determines that the job status of the project branch meets the merge trigger condition and merges the project branch into the system archive branch associated with it.

[0065] In the above embodiment, the automatic merging of code branches can be achieved through the preset merging trigger conditions, further reducing the dependence on manual management and control, and improving the development efficiency of the project.

[0066] In one example, after merging the code branch that meets the merge trigger condition into the upper-level code branch associated therewith, the method further includes: deleting the code branch that meets the merge trigger condition.

[0067] Optionally, after the functional branch that meets the merge triggering condition is merged into the demand branch associated therewith, the functional branch that meets the merge triggering condition is deleted.

[0068] Optionally, after the requirement branch that meets the merge trigger condition is merged into the milestone branch associated therewith, the requirement branch that meets the merge trigger condition is deleted.

[0069] Optionally, after merging the milestone branch that meets the merge trigger condition into the project branch associated therewith, the milestone branch that meets the merge trigger condition is deleted.

[0070] Optionally, after merging the project branch that meets the merge trigger condition into the system archive branch associated therewith, the project branch that meets the merge trigger condition is deleted.

[0071] In one example, after storing the code branches corresponding to each object to be created in the configuration library, it also includes: in response to a branch addition trigger instruction, obtaining incremental requirement information corresponding to the branch addition trigger instruction; the incremental requirement information includes the level identification, object identification and associated information of each object to be added; creating the code branches corresponding to each object to be added according to the source code file and the level identification, object identification and associated information of each object to be added; and storing the code branches corresponding to each object to be added in the configuration library.

[0072] The branch addition trigger instruction is used to trigger the addition of a code branch. Incremental requirement information refers to requirement information added on the basis of the original requirement information, and is used as the basis for adding a new code branch. Each object to be added in the incremental requirement information corresponds to a code branch to be added.

[0073] The implementation method of creating the code branch corresponding to the object to be added is similar to the implementation method of creating the code branch corresponding to the object to be created in the previous embodiment, which will not be repeated here.

[0074] In this embodiment, it is possible to identify incremental requirement information and automatically update code branches, and it is possible to support adjustment and update of the created code branches at all levels by updating the requirement information.

[0075] Figure 3 is a schematic diagram of the structure of a code branch processing device according to an exemplary embodiment. The device can be a software module or a hardware module, or a combination of the two to form a part of a computer device, such as Figure 3 As shown, the device 300 includes:

[0076] The acquisition unit 310 is used to respond to the branch creation trigger instruction and obtain the requirement information corresponding to the branch creation trigger instruction; the requirement information includes the level identification, object identification and association information of each object to be created, wherein the association information is used to indicate the objects that have upper and lower level associations with the object to be created.

[0077] The creation unit 320 is used to create a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created.

[0078] The storage unit 330 is used to store the code branch corresponding to each object to be created in the configuration library.

[0079] In one example, when the creation unit 320 creates a code branch corresponding to each object to be created based on the source code file and the level identification, object identification and associated information of each object to be created, it is specifically used to: divide each object to be created into a project object, a milestone object, a requirement object and a function object according to the level identification of each object to be created; create a project branch according to the source code file and the object identification of the project object; create a milestone branch according to the source code file and the object identification and associated information of the milestone object; create a requirement branch according to the source code file and the object identification and associated information of the requirement object; create a function branch according to the source code file and the object identification and associated information of the function object; wherein, the code branches include project branches, milestone branches, requirement branches and function branches.

[0080] Figure 4 is a schematic diagram of the structure of a code branch processing device according to an exemplary embodiment. Figure 3 Based on the illustrated embodiment, the device 400 further includes:

[0081] The merging unit 340 is used to detect the operation status of each code branch. If it is detected that the operation status of the code branch meets the merging trigger condition, the code branch meeting the merging trigger condition is merged into the upper-level code branch associated therewith.

[0082] In one example, the apparatus 400 further includes:

[0083] The deleting unit 350 is used to delete the code branch that meets the merging triggering condition after merging the code branch that meets the merging triggering condition into the upper-level code branch associated therewith.

[0084] In one example, if the merging unit 340 detects that the job status of a code branch satisfies the merge trigger condition, then the code branch that satisfies the merge trigger condition is merged into the parent code branch associated with it. Specifically, it is used for: if it is detected that the job status of a function branch satisfies the merge trigger condition, then the function branch that satisfies the merge trigger condition is merged into the requirement branch associated with it; if it is detected that the job status of the requirement branch satisfies the merge trigger condition, then the requirement branch that satisfies the merge trigger condition is merged into the milestone branch associated with it; if it is detected that the job status of a milestone branch satisfies the merge trigger condition, then the milestone branch that satisfies the merge trigger condition is merged into the project branch associated with it.

[0085] In one example, if the merging unit 340 detects that the job status of a code branch meets the merge trigger condition, then the code branch that meets the merge trigger condition will be merged into the parent code branch associated with it. It is also used to: if it is detected that the job status of a project branch meets the merge trigger condition, then the project branch that meets the merge trigger condition will be merged into the system archive branch associated with it.

[0086] In one example, the acquisition unit 310 is also used to: in response to a branch addition trigger instruction, obtain incremental requirement information corresponding to the branch addition trigger instruction; the incremental requirement information includes the level identification, object identification and associated information of each object to be added; the creation unit 320 is also used to: create a code branch corresponding to each object to be added according to the source code file and the level identification, object identification and associated information of each object to be added; the storage unit 330 is also used to: store the code branch corresponding to each object to be added to the configuration library.

[0087] For the specific definition of the code branch processing device, please refer to the definition of the code branch processing method above, which will not be repeated here. Each module in the above-mentioned code branch processing device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0088] Figure 5 It is a structural diagram of an electronic device according to an exemplary embodiment, which includes: a processor 501, and a memory 502 communicatively connected to the processor 501; the memory 502 stores computer execution instructions; the processor 501 executes the computer execution instructions stored in the memory 502 to implement the code branch processing method provided in the above embodiment.

[0089] The electronic device further includes a receiver 503 and a transmitter 504. The receiver 503 is used to receive instructions and data sent by an external device, and the transmitter 504 is used to send instructions and data to the external device.

[0090] Figure 6 It is a block diagram of a terminal device according to an exemplary embodiment. The device may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0091] The device 600 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input / output (I / O) interface 612 , a sensor component 614 , and a communication component 616 .

[0092] The processing component 602 generally controls the overall operation of the device 600, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 602 may include one or more modules to facilitate the interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.

[0093] The memory 604 is configured to store various types of data to support operations on the device 600. Examples of such data include instructions for any application or method operating on the device 600, contact data, phone book data, messages, pictures, videos, etc. The memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0094] The power supply component 606 provides power to the various components of the device 600. The power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 600.

[0095] The multimedia component 608 includes a screen that provides an output interface between the device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the device 600 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0096] The audio component 610 is configured to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC), and when the device 600 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 604 or sent via the communication component 616. In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.

[0097] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0098] The sensor assembly 614 includes one or more sensors for providing various aspects of status assessment for the device 600. For example, the sensor assembly 614 can detect the open / closed state of the device 600, the relative positioning of components, such as the display and keypad of the device 600, the sensor assembly 614 can also detect the position change of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, the orientation or acceleration / deceleration of the device 600 and the temperature change of the device 600. The sensor assembly 614 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 614 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

[0099] The communication component 616 is configured to facilitate wired or wireless communication between the device 600 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0100] In an exemplary embodiment, the apparatus 600 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0101] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, and the instructions can be executed by the processor 620 of the device 600 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0102] An embodiment of the present application also provides a non-temporary computer-readable storage medium. When the instructions in the storage medium are executed by a processor of a computer device, the computer device is enabled to execute the method provided in any of the above embodiments.

[0103] An embodiment of the present invention also provides a computer program product, which includes: a computer program, the computer program is stored in a readable storage medium, at least one processor of a computer device can read the computer program from the readable storage medium, and at least one processor executes the computer program so that the computer device executes the method provided in any of the above embodiments.

[0104] It should be understood that the terms "first", "second", etc. in the above embodiments are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. In addition, in the description of this application, unless otherwise specified, the meaning of "multiple" refers to at least two.

[0105] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0106] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A code branch processing method, characterized in that: The method comprises: In response to a branch creation trigger instruction, acquiring requirement information corresponding to the branch creation trigger instruction; the requirement information includes a level identifier, an object identifier, and association information of each object to be created, wherein the association information is used to indicate an object that has a superior-subordinate association with the object to be created; Creating a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created; Storing the code branches corresponding to the objects to be created in the configuration library; Creating a code branch according to the source code file and the level identifier, object identifier and associated information of each object to be created includes: According to the level identification of each object to be created, each object to be created is divided into a project object, a milestone object, a requirement object and a function object; Creating a project branch according to the source code file and the object identifier of the project object; Creating a milestone branch according to the source code file and the object identifier and associated information of the milestone object; Creating a requirement branch according to the source code file and the object identifier and associated information of the requirement object; A functional branch is created according to the source code file and the object identification and association information of the functional object; wherein the code branch includes the project branch, the milestone branch, the requirement branch and the functional branch.

2. The method according to claim 1, characterized in that Also includes: Detecting the operation status of each of the code branches; If it is detected that the job status of the code branch meets the merge trigger condition, the code branch that meets the merge trigger condition is merged into the parent code branch associated with it.

3. The method according to claim 2, characterized in that After merging the code branch that meets the merge triggering condition into the upper-level code branch associated therewith, the method further includes: deleting the code branch that meets the merge triggering condition.

4. The method according to claim 2, characterized in that: If it is detected that the job status of the code branch meets the corresponding merge trigger condition, the code branch that meets the merge trigger condition is merged into the parent code branch associated with it, including: If it is detected that the job status of the function branch meets the merge trigger condition, the function branch that meets the merge trigger condition is merged into the demand branch associated with it; If it is detected that the job status of the demand branch meets the merge trigger condition, the demand branch that meets the merge trigger condition is merged into the milestone branch associated with it; If it is detected that the job status of the milestone branch meets the merge trigger condition, the milestone branch that meets the merge trigger condition will be merged into the project branch associated with it.

5. The method according to claim 4, characterized in that If it is detected that the job status of the code branch meets the corresponding merge trigger condition, the code branch meeting the merge trigger condition is merged into the parent code branch associated therewith, further comprising: If it is detected that the job status of the project branch meets the merge trigger condition, the project branch that meets the merge trigger condition will be merged into the system archive branch associated with it.

6. The method according to any one of claims 1 to 5, characterized in that Also includes: In response to a branch adding trigger instruction, obtaining incremental demand information corresponding to the branch adding trigger instruction; the incremental demand information includes a level identifier, an object identifier and associated information of each object to be added; Creating a code branch corresponding to each of the objects to be added according to the source code file and the level identifier, object identifier and associated information of each of the objects to be added; The code branches corresponding to the objects to be added are stored in the configuration library.

7. A code branch processing device, characterized in that: The device comprises: an acquisition unit, configured to acquire, in response to a branch creation trigger instruction, demand information corresponding to the branch creation trigger instruction; the demand information includes a level identifier, an object identifier, and association information of each object to be created, wherein the association information is used to indicate an object that has a superior-subordinate association with the object to be created; A creation unit, used to create a code branch corresponding to each object to be created according to the source code file and the level identifier, object identifier and associated information of each object to be created; A storage unit, used for storing the code branches corresponding to the objects to be created in a configuration library; The creation unit is specifically used to divide each object to be created into a project object, a milestone object, a requirement object and a function object according to the level identification of each object to be created; create a project branch according to the source code file and the object identification of the project object; create a milestone branch according to the source code file and the object identification and associated information of the milestone object; create a requirement branch according to the source code file and the object identification and associated information of the requirement object; create a function branch according to the source code file and the object identification and associated information of the function object; wherein the code branch includes the project branch, the milestone branch, the requirement branch and the function branch.

8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images