Management method and device for projects in warehouse and storage medium

Abstract

The invention relates to the technical field of data processing, in particular to a management method and device for projects in a warehouse and a storage medium. Comprising the following steps: when a management request of a first client for projects in a remote warehouse is received, acquiring projects stored in a plurality of remote warehouses; the plurality of remote warehouses are warehouses corresponding to development tasks and are used for storing projects corresponding to the development tasks, one remote warehouse correspondingly stores one project, and when the projects stored in the plurality of remote warehouses are all operated, the development tasks are realized; pushing the items stored in the plurality of remote warehouses to a first client, so that the first client displays the items stored in the plurality of remote warehouses as a plurality of items of a local warehouse; and after determining that the first client performs a target operation on a target item in the plurality of items of the local warehouse, synchronizing the target item subjected to the target operation to the corresponding remote warehouse. The embodiment of the invention is used for improving the warehouse project management efficiency.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a management method, device and storage medium for items in a warehouse. Background Art

[0002] In the process of front-end development, the version code can be stored and managed through the warehouse project shared by the team, such as the project of the git warehouse, to improve the efficiency of team development. Currently, the management of projects in these warehouses is usually done manually, which is inefficient and prone to errors. Therefore, there is an urgent need for a solution to warehouse project management. Summary of the invention

[0003] In order to solve the above technical problems, the present application provides a management method, device and storage medium for projects in a warehouse, which can solve the problem of low efficiency in current micro-frontend project management.

[0004] In the first aspect, the present application provides a method for managing projects in a warehouse, which is applied to a server, including: upon receiving a management request for projects in a remote warehouse from a first client, obtaining projects stored in multiple remote warehouses; the multiple remote warehouses are warehouses corresponding to development tasks, which are used to store projects corresponding to the development tasks, and one remote warehouse stores one project correspondingly, and when the projects stored in the multiple remote warehouses are all run, the development task is realized; the projects stored in the multiple remote warehouses are pushed to the first client, so that the first client displays the projects stored in the multiple remote warehouses as multiple projects in the local warehouse; after determining that the first client performs a target operation on a target project in the multiple projects in the local warehouse, the target project after the target operation is performed is synchronized to the corresponding remote warehouse.

[0005] In the second aspect, the present application provides a management device for projects in a warehouse, which is applied to a server, and includes: a receiving module, which is used to obtain projects stored in multiple remote warehouses when receiving a management request for projects in a remote warehouse from a first client; multiple remote warehouses are warehouses corresponding to development tasks, which are used to store projects corresponding to development tasks, and one remote warehouse stores one project corresponding to development tasks, and when the projects stored in multiple remote warehouses are all run, the development task is realized; a sending module, which is used to push the projects stored in multiple remote warehouses to the first client, so that the first client displays the projects stored in multiple remote warehouses as multiple projects in the local warehouse; a determination module, which is used to determine that after the first client performs a target operation on a target project in multiple projects in the local warehouse, the target project after the target operation is performed is synchronized to the corresponding remote warehouse.

[0006] On the third aspect, the present application provides a method for managing projects in a warehouse, which is applied to a first client, including: in response to a management operation of a project in a remote warehouse triggered by a user, establishing communication with a server, and sending a management request for the project in the remote warehouse to the server; the remote warehouse is a warehouse corresponding to the development task, and is used to store multiple projects corresponding to the development task, and one remote warehouse corresponds to storing one project; when the projects stored in multiple remote warehouses are all run, the development task is implemented; multiple projects of the remote warehouse pushed by the server are received, and the multiple projects are displayed as multiple projects of the local warehouse; in response to a target operation triggered by the user on a target project in multiple projects in the local warehouse, the target operation is performed on the target project, and the target project after the target operation is synchronized to the server.

[0007] In a fourth aspect, the present application provides a device for managing projects in a warehouse, which is applied to a first client and includes: a processing module, which is used to establish communication with a server in response to a management operation of a project in a remote warehouse triggered by a user, and send a management request for the project in the remote warehouse to the server; the remote warehouse is a warehouse corresponding to a development task, which is used to store multiple projects corresponding to the development task, and one remote warehouse stores one project; when the projects stored in multiple remote warehouses are all run, the development task is implemented; a display module, which is used to receive multiple projects of the remote warehouse pushed by the server, and display the multiple projects as multiple projects of the local warehouse; an execution module, which is used to respond to a target operation triggered by a user on a target project in multiple projects in the local warehouse, execute the target operation on the target project, and synchronize the target project after the target operation to the server.

[0008] In a fifth aspect, the present application provides an electronic device comprising: a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the method for managing items in a warehouse according to the first aspect or the third aspect is implemented.

[0009] In a sixth aspect, the present application provides a computer-readable storage medium, comprising: a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements the method for managing items in a warehouse as in the first aspect or the third aspect.

[0010] In a seventh aspect, the present application provides a computer program product, comprising: when the computer program product runs on a computer, the computer implements the method for managing items in a warehouse as in the first aspect or the third aspect.

[0011] The technical solution provided by the present application has the following advantages over the prior art: First, the first client responds to the management operation of the project in the remote warehouse triggered by the user, establishes communication with the server, and sends a management request for the project in the remote warehouse to the server. Afterwards, when the server receives the management request for the project in the remote warehouse from the first client, it obtains the projects stored in multiple remote warehouses and pushes the projects stored in multiple remote warehouses to the first client. Among them, multiple remote warehouses are warehouses corresponding to development tasks, which are used to store projects corresponding to development tasks. One remote warehouse stores one project correspondingly. When the projects stored in multiple remote warehouses are all run, the development task is realized. Afterwards, the first client receives multiple projects of the remote warehouse pushed by the server, and displays the multiple projects as multiple projects of the local warehouse. The first client responds to the target operation triggered by the user on the target project in multiple projects of the local warehouse, performs the target operation on the target project, and synchronizes the target project after the target operation to the server. Finally, after the server determines that the first client performs the target operation on the target project in multiple projects of the local warehouse, it synchronizes the target project after the target operation to the corresponding remote warehouse. In this way, on the one hand, the server is used as a proxy between the first client and the remote warehouse, and the first client can directly manage the projects in the remote warehouse through the server, avoiding the problem of low efficiency and easy errors when manually maintaining the projects in the remote warehouse, thereby improving the management efficiency of the projects in the remote warehouse. On the other hand, the server acts as a proxy between the first client and the remote warehouse. After the first client manages and modifies the projects in the local warehouse, it can synchronize the modified projects in the local warehouse to the remote warehouse in a timely manner, so that other team collaborators corresponding to the remote warehouse can timely understand the modifications made by the users of the first client to the projects in the remote warehouse, thereby improving the efficiency of team collaboration.

[0012] In this application, the names of the above devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear with other names. As long as the functions of each device or functional module are similar to those of this application, they are within the scope of protection of this application.

[0013] These and other aspects of the present application will become more apparent from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] 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.

[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0016] Figure 1 One of the flowcharts of the method for managing items in a warehouse provided in an embodiment of the present application;

[0017] Figure 2 One of the display interface schematic diagrams is provided for the embodiment of the present application;

[0018] Figure 3 Provides a second display interface schematic diagram for an embodiment of the present application;

[0019] Figure 4 The second flowchart of the method for managing items in a warehouse provided in an embodiment of the present application;

[0020] Figure 5 The third flowchart of the method for managing items in a warehouse provided in an embodiment of the present application;

[0021] Figure 6 One of the structural schematic diagrams of the management device for items in a warehouse provided in an embodiment of the present application;

[0022] Figure 7 The second structural diagram of the device for managing items in a warehouse provided in an embodiment of the present application;

[0023] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to more clearly understand the above-mentioned purposes, features and advantages of the present application, the scheme of the present application will be further described below. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

[0025] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only part of the embodiments of the present application, rather than all of the embodiments.

[0026] First, some nouns or terms involved in the embodiments of the present application are explained below.

[0027] Warehouse: used to store multiple projects corresponding to development tasks. When the projects stored in multiple remote warehouses are all run, the development tasks are realized. For example, in git, all files and historical versions of a project are stored in a warehouse. Each warehouse contains the complete history of the project and the current status of all files. Warehouses are usually divided into remote warehouses and local warehouses.

[0028] Remote repository: A remote repository is a copy of a repository stored on a remote server and can be used for collaborative development by multiple people. The remote repository retains the version history of the entire project. Developers can view, restore, or roll back to a previous software version by operating the project in the remote repository.

[0029] Local repository: A local repository is a copy of a repository stored on a local computer. It contains complete project history, project branches, project commits, and other information. Local repositories are usually used by developers to modify, commit, and perform version control operations on their local code. Developers can create project branches, merge project branches, and commit changes in local repositories. All of these operations do not require a network connection, but are performed locally.

[0030] The following is a detailed description of the management method, device and storage medium for items in a warehouse provided by the embodiments of the present application through specific embodiments in conjunction with the accompanying drawings.

[0031] The management device for items in the warehouse provided in the embodiment of the present application can be hardware or software. When the management device for items in the warehouse is hardware, it can be various electronic devices with management functions for items in the warehouse, including but not limited to televisions, tablet computers, smart watches, computers, smart phones, AI devices, robots, smart vehicles, etc. When the management device for items in the warehouse is software, it can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules, or it can be implemented as a single software or software module. It is not specifically limited here.

[0032] Figure 1 A flowchart of a method for managing items in a warehouse provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method for managing items in a warehouse may include the following steps.

[0033] S11. The first client establishes communication with the server in response to a management operation of a project in a remote warehouse triggered by a user.

[0034] Among them, multiple remote warehouses are warehouses corresponding to development tasks, which are used to store projects corresponding to the development tasks. One remote warehouse stores one project correspondingly. When the projects stored in multiple remote warehouses are all run, the development task is realized.

[0035] First, a user triggers a project management operation in a remote repository on a first client.

[0036] In some embodiments, the user triggers a project management operation in a remote repository by clicking an option in a navigation menu; or by clicking controls and links; or by dragging and dropping interface elements, etc. This application does not limit this.

[0037] Secondly, the first client establishes communication with the server. In some embodiments, the first client can establish socket communication with the server.

[0038] S12: The first client sends a management request for a project in a remote warehouse to the server.

[0039] Specifically, the first client may send a management request for the project in the remote warehouse to the server through the communication established between the first client and the server.

[0040] S13. When receiving a management request for a project in a remote warehouse from the first client, the server obtains the projects stored in the multiple remote warehouses.

[0041] Specifically, the server obtains the items stored in the multiple remote repositories by obtaining the items stored in the remote repositories from the interface corresponding to the remote repositories. For example, when the remote repositories are git repositories, the interface corresponding to the git repositories may be the gitlab application programming interface (Application Programming Interface, API).

[0042] S14. The server pushes the projects stored in the multiple remote warehouses to the first client.

[0043] The items stored in the multiple remote warehouses are used to instruct the first client to display the items stored in the multiple remote warehouses as multiple items in the local warehouse.

[0044] Specifically, the server may push the projects corresponding to the multiple remote repositories to the first client through the communication established between the server and the first client.

[0045] S15. The first client receives the multiple projects of the remote warehouse pushed by the server, and displays the multiple projects as multiple projects of the local warehouse.

[0046] Specifically, the first client may display multiple items of the remote warehouse pushed by the server in a preset display mode, such as a list view, a grid view, a card view, etc.

[0047] S16: The first client performs a target operation on a target project in multiple projects in the local warehouse in response to a target operation triggered by the user.

[0048] First, when displaying multiple projects in the local warehouse, the first client can also display an operation control for performing a target operation on the multiple projects in the local warehouse as an operation entry for the target operation. Figure 2 As shown, when the first client displays multiple projects (such as Project 1, Project 2, Project 3, Project 4, etc.) in the local warehouse, it also displays a create label operation control for creating labels for multiple projects; a batch replace operation control for replacing files (or folders) in multiple projects with files (or folders) in other paths; of course, more operation controls can be displayed, such as Figure 2 The XX operation control shown in the figure. For different target operations, the methods of managing target items are different.

[0049] Secondly, the first client can display an operation interface in response to a trigger operation for an operation entry corresponding to the target operation. The operation interface may include identifiers of multiple items, a selection control corresponding to each item, and a confirmation operation control. The identifier of the item is used to uniquely represent the item, for example, it may be the name of the item, the number of the item, etc. The selection control is used to indicate that the item corresponding to the selection control is selected as the target item when the user clicks on it; at least one target item can be selected for one target operation, for example, in Figure 3 In the operation interface shown, the user selects Project 1 and Project 2, and Project 1 and Project 2 are target projects. Different operation controls can correspond to different confirmation operation controls. For example, when the operation control is a delete operation control, the corresponding confirmation operation control is a confirm delete control; when the operation control is a create tag operation control, the corresponding confirmation operation control is a create control; when the operation control is a batch replace operation control, the corresponding confirmation operation control is a replace control, etc.

[0050] In some embodiments, the operation interface may also include an input box operable by the user for inputting corresponding information, which will be used to assist in executing the target operation after the user triggers the confirmation operation control. For example, when the confirmation operation control is a confirmation deletion control, the user may enter the name of the file (or folder) to be deleted in the corresponding input box to indicate that the file (or folder) with the same name as the one entered in the input box is to be deleted in the target project; when the confirmation operation control is a creation control, the user may enter a label in the corresponding input box to indicate that the label entered in the input box is added to the target project; when the confirmation operation control is a replacement control, the user may enter the address of the replacement file (or folder) and the address of the replaced file (or folder) in the corresponding input box to indicate that the file (or folder) corresponding to the address of the replaced file (or folder) in the target project is replaced with the file (or folder) corresponding to the address of the replacement file (or folder), etc.

[0051] Finally, the first client performs the target operation on the target item selected by the user in response to the trigger operation on the confirmation operation control. Specifically, the way to perform the target operation on the target item may be to perform different operations according to different confirmation operation controls. For example, when the confirmation operation control is a confirmation deletion control, the way to perform the target operation on the target item may be to delete the target item; when the confirmation operation control is a creation control, the way to perform the target operation on the target item may be to add a preset label or a label input by the user to the target item; when the confirmation operation control is a replacement control, the way to perform the target operation on the target item may be to replace the target item with the item in the target address, etc.

[0052] S17: The first client synchronizes the target item after the target operation to the server.

[0053] S18. After determining that the first client performs a target operation on a target project among multiple projects in the local warehouse, the server synchronizes the target project after the target operation is performed to the corresponding remote warehouse.

[0054] Specifically, when the server receives the target project after executing the target operation sent by the first client, it determines that the first client has executed the management operation on the target project. After that, the target project after executing the management operation is synchronized to the corresponding remote warehouse from the interface corresponding to the remote warehouse. In some embodiments, the interface for synchronizing the target project after executing the target operation is different from the interface for obtaining the corresponding projects of multiple remote warehouses.

[0055] In the above scheme, first, the first client responds to the management operation of the project in the remote warehouse triggered by the user, establishes communication with the server, and sends a management request for the project in the remote warehouse to the server. Afterwards, when the server receives the management request for the project in the remote warehouse from the first client, it obtains the projects stored in multiple remote warehouses and pushes the projects stored in multiple remote warehouses to the first client. Among them, multiple remote warehouses are warehouses corresponding to development tasks, which are used to store projects corresponding to development tasks. One remote warehouse stores one project. When the projects stored in multiple remote warehouses are all run, the development task is realized. Afterwards, the first client receives multiple projects of the remote warehouse pushed by the server, and displays the multiple projects as multiple projects of the local warehouse. In response to the target operation triggered by the user on the target project in the multiple projects of the local warehouse, the first client performs the target operation on the target project, and synchronizes the target project after the target operation to the server. Finally, after the server determines that the first client performs the target operation on the target project in the multiple projects of the local warehouse, it synchronizes the target project after the target operation to the corresponding remote warehouse. In this way, on the one hand, the server is used as a proxy between the first client and the remote warehouse, and the first client can directly manage the projects in the remote warehouse through the server, avoiding the problem of low efficiency and easy errors when manually maintaining the projects in the remote warehouse, thereby improving the management efficiency of the projects in the remote warehouse. On the other hand, the server acts as a proxy between the first client and the remote warehouse. After the first client manages and modifies the projects in the local warehouse, it can synchronize the modified projects in the local warehouse to the remote warehouse in a timely manner, so that other team collaborators corresponding to the remote warehouse can timely understand the modifications made by the users of the first client to the projects in the remote warehouse, thereby improving the efficiency of team collaboration.

[0056] In some embodiments, the method for managing projects in a warehouse further includes: the server establishing communication with a plurality of first clients, and upon detecting a change in a project in any remote warehouse, pushing the changed project to all first clients.

[0057] First, the server establishes communication with multiple first clients. Among them, the first client is a client that has the authority to manage projects in multiple repositories. Specifically, in order to improve development efficiency, front-end development is usually a multi-person collaborative development model. Therefore, before receiving the management request of the first client for the project in the remote warehouse, it is necessary to establish communication between the multiple first clients and the server. Furthermore, in order to enable both the first client and the server to actively trigger communication with the other end, the server establishes two-way communication with the multiple first clients. For example, socket communication.

[0058] In the above scheme, the server can establish two-way communication with multiple first clients, so that the server can also actively initiate the push of project business in the remote warehouse of the first client, instead of returning the corresponding request response to the first client only after receiving the request of the first client. This enables the server to automatically trigger the management of projects in the remote warehouse when the projects in the remote warehouse change, thereby improving the management efficiency of projects in the warehouse.

[0059] Secondly, when the server detects that an item in any remote repository has changed, it pushes the changed item to all first clients.

[0060] In some embodiments, the server detects whether a remote warehouse item has changed by calling a monitoring program through a relevant interface corresponding to the remote warehouse to monitor data changes corresponding to the remote warehouse item to detect changes in the remote warehouse item; or by setting Webhooks to detect changes in the remote warehouse item. In some embodiments, the interface for detecting whether a remote warehouse item has changed is different from the interface for synchronizing the modified target item and the interface for obtaining items corresponding to multiple remote warehouses.

[0061] In the above solution, when the server detects changes in the remote warehouse, it can actively push the changed items in the remote warehouse to the first client, ensuring the consistency of project data between the first client and the remote warehouse, and indirectly improving team collaboration efficiency.

[0062] In some embodiments, the method for managing items in a warehouse further includes: when the server detects that there are abnormal items in the remote warehouse, the server pushes an abnormal prompt to the first client.

[0063] The abnormal prompt is used to instruct the first client to suspend operations on abnormal projects in the local warehouse. Projects that include at least one of the following are identified as abnormal projects: the project contains unreviewed code; the project contains duplicate project tags; the project contains unmerged project branches. Unmerged project branches refer to project branches that have been created but have not yet been integrated back into the main project.

[0064] In some embodiments, the server detects whether there are abnormal items by calling an abnormality detection program through the relevant interface corresponding to the remote warehouse to monitor whether the remote warehouse items are abnormal; or by using relevant tools to detect whether the remote warehouse items are abnormal. In some embodiments, the interface for detecting whether the remote warehouse items are abnormal is different from the interface for detecting whether the remote warehouse items have changed, the interface for synchronizing the modified target items, and the interface for obtaining the corresponding items of multiple remote warehouses.

[0065] In the above scheme, when the server detects that there are abnormal projects in the remote warehouse, it can actively push abnormal prompts to the first client, so that the first client can suspend operations on abnormal projects in time, avoiding the low efficiency and easy error problems when manually maintaining projects in the remote warehouse, thereby improving the management efficiency of projects in the warehouse.

[0066] In some embodiments, the first client and the server establish communication in a manner that the first client and the server establish two-way communication.

[0067] Specifically, in order to enable both the first client and the server to actively trigger communication with the other end, the first client establishes two-way communication with multiple servers, for example, socket communication.

[0068] In some embodiments, the method for managing projects in a repository further includes: the first client receives a changed project of the remote repository pushed from the server, and replaces the current project with the changed project.

[0069] The current project is a project in the local repository that has the same identifier as the changed project.

[0070] Specifically, the method of replacing the current project with the changed project can be that the server pushes the identifier of the changed project when pushing the changed project. After that, the first client determines the current project according to the identifier of the changed project and replaces the current project with the changed project. The method of replacing the current project with the changed project can also be achieved through subsequent steps S164-S167.

[0071] In the above solution, the first client receives the changed project pushed from the server and replaces the current project with the changed project, thereby ensuring the consistency of project data between the local warehouse of the first client and the remote warehouse, and indirectly improving the efficiency of team collaboration.

[0072] In some embodiments, the method for managing projects in a warehouse further includes: when the first client receives an abnormal prompt pushed from the server, the first client displays the abnormal prompt and prohibits the execution of a triggering operation of an abnormal project corresponding to the abnormal prompt.

[0073] Specifically, the abnormal prompt may include an identifier corresponding to the abnormal item. When the first client receives the abnormal prompt pushed from the server, it prohibits the execution of the triggering operation of the abnormal item corresponding to the abnormal prompt according to the identifier corresponding to the abnormal item.

[0074] In some embodiments, the method of prohibiting the execution of the trigger operation of the abnormal item corresponding to the abnormal prompt can be that when the first client receives the abnormal prompt pushed from the server, the operation entry corresponding to the abnormal item is not displayed; or the operation entry corresponding to the abnormal item is displayed, but it cannot be operated.

[0075] In the above scheme, when the first client receives the exception prompt pushed from the server, it displays the exception prompt and prohibits the execution of the trigger operation of the abnormal project corresponding to the exception prompt, thereby avoiding the problem of low efficiency and easy errors when manually maintaining the warehouse projects, and improving the management efficiency of the projects in the warehouse.

[0076] In some embodiments, Figure 4 As shown, when the target operation is a tag adding operation, in response to a target operation triggered by a user on a target project among multiple projects in a local warehouse, a method of performing the target operation on the target project may include the following steps:

[0077] S161: In response to a tag adding operation triggered by a user for a target project among multiple projects in a local warehouse, the first client displays a tag information input box.

[0078] For example, if a user Figure 2 The operation interface shown in the figure triggers the creation of a label control, and Figure 3 The operation interface shown in the figure selects Project 1 and Project 2 as the target projects. Figure 3 The operation interface shown displays a label information input box 31 .

[0079] S162. The first client determines whether the tag information input by the user in the tag information input box satisfies a preset classification, and executes step S163 if the tag information input by the user satisfies the preset classification; and executes step S164 if the tag information input by the user does not satisfy the preset classification.

[0080] The tag information is used to identify and / or describe the target project. For example, the tag information may include tag content, or the tag information may include tag content and tag description. The tag description may be a CR link corresponding to the project, an online application link, etc.

[0081] The classification is the classification corresponding to the target project, which is used to limit the input scope of the tag information. Projects corresponding to front-end development can usually be divided into multiple types such as new demand projects, problem fixing projects, daily maintenance projects, collection branch online projects, etc.; therefore, in order to achieve standardized management of front-end project labels, the tag information entered by the user can be restricted to the corresponding classification for easy management. Therefore, when it is detected that the tag information entered by the user is not in the pre-set classification, the first prompt information can be displayed to prompt the user that the content entered does not meet the requirements, so that the user can re-enter the content into the tag input box.

[0082] The first client determines whether the tag information input by the user satisfies the preset classification by detecting whether the tag content input by the user includes a preset field, and when the tag content includes the preset field, determining that the tag information satisfies the preset classification; when the tag content does not include the preset field, determining that the tag information does not satisfy the preset classification. Specifically, the method for detecting whether the tag content input by the user includes the preset field may be to match the tag content with the preset field, and when any preset field is matched, determining that the tag content includes the preset field; when no preset field is matched, determining that the tag content does not include the preset field.

[0083] Among them, the preset fields are default characters, or characters pre-written by relevant personnel according to actual conditions. For example, when the preset fields are "new requirements", "updated version", or "configuration changes", and the tag content entered by the user is "modify the problem", since the field "modify the problem" does not exist in the preset fields, at this time, it is determined that the tag content does not include the preset fields. For another example, when the preset fields are "vipdev" or "integral", and the tag name entered by the user is "tag_vipdev-abc", it can be seen that "tag_vipdev-abc" includes the preset field "vipdev". At this time, it is determined that the tag content includes the preset field.

[0084] S163: Generate a tag record according to the tag information and target item input by the user.

[0085] Among them, the tag record is used to associate the target project with the tag information.

[0086] Specifically, when the tag information includes tag content, a tag record is generated according to the tag content and target item input by the user. When the tag information includes tag content and tag description, a tag record is generated according to the tag content and tag description input by the user and the target item.

[0087] Further, a method of generating a tag record based on the tag content and target project input by the user may be to store a tag record in the tag column and establish a connection relationship between the tag record and the target project. The tag record includes the tag content input by the user. A method of generating a tag record based on the tag content, tag description, and target project input by the user may be to store a tag record in the tag column and establish a connection relationship between the tag record and the target project. The tag record includes the tag content and tag description input by the user.

[0088] Furthermore, the connection relationship between the tag record and the target item can be established by calling the corresponding connection relationship establishment method in the preset interface to establish the connection relationship between the tag record and the target item; or the connection relationship between the tag record and the selected target item can be established by maintaining a connection relationship table.

[0089] S164: Display the first prompt information.

[0090] The first prompt information is used to prompt the user to re-enter the label information.

[0091] In the above scheme, when the tag information input by the user meets the preset classification, the first client generates a tag record according to the tag information input by the user and the target project; when the tag information input by the user does not meet the preset classification, the first prompt information is displayed. In this way, on the one hand, it is possible to generate a tag record for the target project according to the tag information input by the user, thereby realizing the operation of batch management of warehouse project tags and improving the efficiency of warehouse project management. On the other hand, when creating tags, for some projects, it is possible to allow the addition of corresponding tag descriptions, which facilitates the unified management across projects, simplifies the management process of multi-project tags and tag descriptions, and improves the efficiency of collaboration between projects. On the other hand, it is possible to standardize the content entered by the user in the tag input box, so as to facilitate the targeted management and maintenance of projects in teamwork and improve the efficiency of teamwork.

[0092] In some embodiments, Figure 5 As shown, when the target operation is a replacement operation, in response to a target operation triggered by a user on a target project among multiple projects in a local warehouse, a method of performing the target operation on the target project may include the following steps:

[0093] S165: In response to a replacement operation triggered by a user for a target project among multiple projects in a local repository, the first client obtains a directory structure of the target project, a target path and a source file name input by the user.

[0094] First, the first client obtains the directory structure of the target project.

[0095] Specifically, the first client obtains the directory structure of the target project by calling the relevant interface to obtain the directory structure corresponding to each target project; or by obtaining the directory structure corresponding to each target project through the identifier corresponding to the target project; or the project name of the target project may include the directory structure corresponding to the target project, so that the directory structure corresponding to the target project can be obtained by directly reading the project name of the target project; this application does not limit this.

[0096] Secondly, the first client obtains the target path and source file name input by the user.

[0097] In some embodiments, the operation interface may include a target path input box and a source file name input box operable by the user. The first client obtains the target path and the source file name input by the user by obtaining the target path input box and the source file name input by the user in the target path input box and the source file name input box.

[0098] S166: The first client reads the target file according to the target path.

[0099] Specifically, the first client reads the target file according to the target path by accessing the target path and reading the corresponding target file in the target path.

[0100] S167: The first client determines the actual address of the source file in the target project according to the directory structure and the source file name input by the user.

[0101] Specifically, the directory structure of the target project includes the specific location corresponding to each file (or folder) in the target project. Therefore, according to the directory structure of the target project and the input source file name, the actual address of the source file in the target project can be obtained. For example, the input source file name entered by the user is 1; the target project includes the first project and the second project; the directory structure of the first project includes: wew / fre / dewa / hii / 1; wew / fre / dewa / hii / 2; wew / fre / dewa / hii / 3; the directory structure of the second project includes: wew / fs / tyd / fewrf / 1; wew / fs / tyd / fewrf / 4; wew / fs / tyd / fewrf / 5; then, according to the directory structure of the first project and the input source file name 1, the actual address of the source file in the first project is determined to be: wew / fre / dewa / hii / 1; according to the directory structure of the second project and the input source file name 1, the actual address of the source file in the second project is determined to be: wew / fs / tyd / fewrf / 1. Of course, the above directories and file names are only examples. In actual applications, the directories of the target projects are usually more complicated, but the principles are the same.

[0102] S168: The first client accesses the actual address and replaces the source file in the actual address with the target file.

[0103] In the above scheme, the first client can determine the actual address of the source file in the target project based on the directory structure and the source file name entered by the user. In this way, no matter whether the user enters the source file name or the address of the source file, the actual address of the source file can be dynamically obtained, which simplifies the user operation steps, enables users to easily select and manage projects, and improves management efficiency.

[0104] In some embodiments, before reading the target file according to the target path input by the user, the method for managing projects in the warehouse also includes: the first client displays a second prompt message when the target path input by the user and the source file name meet at least one of the following constraints (1) to (3).

[0105] The second prompt information is used to prompt the user to re-enter the target path and / or source file name. The constraints include: (1) the target path is the same as the source file name; (2) the source file name ends with a slash; (3) the target path is not a single slash, and the target path ends with a slash.

[0106] Specifically, if the target path entered by the user is the same as the source file name, it means that the corresponding file (or folder) does not need to be replaced. At this time, a second prompt message is displayed to remind the user that the target path and / or source file name need to be re-entered. Secondly, if the source file name ends with a slash, it means that the user entered a directory, not a file name. When matching the directory structure of the selected item, it cannot be matched to a fixed actual address. Therefore, a second prompt message is displayed to remind the user that the source file name needs to be re-entered. Finally, if the target path is not a single slash, and the target path ends with a slash, a second prompt message is displayed to remind the user that the target path needs to be re-entered.

[0107] For example, the following code can be used to determine that when the target path and source file name input by the user meet constraint condition (1), the second prompt information is displayed, and the second prompt information is: the target path and source file name are consistent, please check.

[0108] if(sourcePath,substring(0,sourcePath.lastIndex0f(" / "))===targetPath||sourcePath===targetPath){enqueueSnackbar("The target path and source file name are consistent, please check",{variant:"error"});return;}.

[0109] For another example, the following code can be used to determine that when the target path and source file name input by the user meet constraint condition (2) or (3), a second prompt message is displayed, and the second prompt message is: the directory format is illegal.

[0110] if

[0111] (sourcePath[sourcePath.length-1]===" / "||(targetPath!==" / "&&targetPath[targetP ath.length-1]===" / "){enqueueSnackbar("Invalid directory format", {variant:"error"}); return;}.

[0112] In the above scheme, the formats of the target path and source file names input by the user can be judged, avoiding the situation where batch replacement occurs abnormally due to abnormal target path and source file names input by the user, and ensuring the correct implementation of the warehouse project management method.

[0113] In some embodiments, the project management method in the warehouse provided by the present application can be applied to front-end development scenarios and can also be used in micro-front-end development scenarios.

[0114] In some embodiments, React and TypeScript can be used to build a user interface, and the directory structure of the project can be input or selected through a form or file selector. After the target path and source file name entered by the user are verified, the first client can pass the page information to the server through the socket, and the server performs modification operations on the project selected by the user according to the page information. In this way, modification operations can be defined on the first client, and the server converts these operations into executable tasks according to the page information and executes them, which greatly reduces manual operations and human errors, and realizes batch and efficient management of remote warehouse projects on the front end.

[0115] In some embodiments, the micro frontend and the backend service use Socket.IO to achieve real-time communication between the client and the server. In this way, the client interface can update the execution progress and status of the batch operation task in real time, improving the interactivity and user experience of the system; users can promptly discover and handle problems that arise during the batch operation process, reducing delays and errors in the operation process.

[0116] The embodiment of the present application can divide the functional modules of the management device of the items in the warehouse according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0117] like Figure 6FIG. 6 is a schematic diagram of a structure of a management device for items in a warehouse provided by an embodiment of the present application. The management device for items in a warehouse is applied to a server, and includes a receiving module 61 , a sending module 62 , and a determining module 63 .

[0118] The receiving module 61 is used to obtain the projects stored in multiple remote warehouses when receiving the management request of the first client for the projects in the remote warehouse; the multiple remote warehouses are warehouses corresponding to the development tasks, which are used to store the projects corresponding to the development tasks, and one remote warehouse corresponds to storing one project. When the projects stored in the multiple remote warehouses are all run, the development task is realized; the sending module 62 is used to push the projects stored in the multiple remote warehouses to the first client, so that the first client can display the projects stored in the multiple remote warehouses as multiple projects of the local warehouse; the determining module 63 is used to determine that after the first client performs a target operation on the target project in the multiple projects of the local warehouse, the target project after the target operation is performed is synchronized to the corresponding remote warehouse.

[0119] In some embodiments, the management device for projects in the warehouse also includes an establishment module 64; the establishment module 64 is used to establish communication with multiple first clients; the sending module 62 is also used to push the changed projects to all first clients when a change is detected in a project in any remote warehouse.

[0120] In some embodiments, the sending module 62 is also used to push an abnormal prompt to the first client when an abnormal project is detected in the remote repository; the abnormal prompt is used to instruct the first client to suspend operations on abnormal projects in the local repository; wherein, a project including at least one of the following is determined to be an abnormal project: there is unreviewed code in the project; there are duplicate project tags in the project; there are unmerged project branches in the project; an unmerged project branch refers to a project branch that has been created but has not yet been integrated back into the main project.

[0121] The management device for items in a warehouse provided in this embodiment can execute the management method for items in a warehouse provided in the above method embodiment. Its implementation principle and technical effects are similar to those of the above method and will not be repeated here.

[0122] like Figure 7 FIG. 1 is a schematic diagram of a structure of a device for managing items in a warehouse provided by an embodiment of the present application. The device for managing items in a warehouse is applied to a first client and includes a processing module 71 , a display module 72 , and an execution module 73 .

[0123] The processing module 71 is used to establish communication with the server in response to the management operation of the project in the remote warehouse triggered by the user, and send a management request for the project in the remote warehouse to the server; the remote warehouse is the warehouse corresponding to the development task, which is used to store multiple projects corresponding to the development task, and one remote warehouse corresponds to storing one project; when the projects stored in multiple remote warehouses are all run, the development task is realized; the display module 72 is used to receive multiple projects of the remote warehouse pushed by the server, and display the multiple projects as multiple projects of the local warehouse; the execution module 73 is used to respond to the target operation triggered by the user on the target project in the multiple projects of the local warehouse, execute the target operation on the target project, and synchronize the target project after the target operation to the server.

[0124] In some embodiments, the processing module 71 is further used to receive a changed project of a remote repository pushed from a server, and replace the current project with the changed project; the current project is a project in multiple projects of the local repository with the same identifier as the changed project.

[0125] In some embodiments, the execution module 73 is specifically used to: when the target operation is a tag adding operation, in response to the user triggering a tag adding operation for a target project among multiple projects in a local warehouse, display a tag information input box; when the tag information entered by the user in the tag information input box meets a preset classification, generate a tag record based on the tag information entered by the user and the target project; the tag information is used to identify and\or describe the target project; the classification is a classification corresponding to the target project; the tag record is used to associate the target project and the tag information; when the tag information entered by the user in the tag information input box does not meet the preset classification, display a first prompt message; the first prompt message is used to prompt to re-enter the tag information.

[0126] In some embodiments, the execution module 73 is specifically used to: when the target operation is a replacement operation, in response to the replacement operation triggered by the user for a target project in multiple projects in the local warehouse, obtain the directory structure of the target project, the target path and source file name input by the user; read the target file according to the target path; determine the actual address of the source file in the target project according to the directory structure and the source file name input by the user; access the actual address, and replace the source file in the actual address with the target file.

[0127] The management device for items in a warehouse provided in this embodiment can execute the management method for items in a warehouse provided in the above method embodiment. Its implementation principle and technical effects are similar to those of the above method and will not be repeated here.

[0128] Figure 8An electronic device according to an exemplary embodiment may include a processor 802, and the processor 802 is used to execute application code to implement the method for managing items in a warehouse in the present application.

[0129] The processor 802 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0130] like Figure 8 As shown, the electronic device may further include a memory 803. The memory 803 is used to store application program codes for executing the solution of the present application, and the execution is controlled by the processor 802.

[0131] The memory 803 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic 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 thereto. The memory 803 may exist independently and be connected to the processor 802 via the bus 804. The memory 803 may also be integrated with the processor 802.

[0132] like Figure 8 As shown, the electronic device may further include a communication interface 801, wherein the communication interface 801, the processor 802, and the memory 803 may be coupled to each other, for example, via a bus 804. The communication interface 801 is used to exchange information with other devices, for example, to support information exchange between the electronic device and other devices.

[0133] It should be pointed out that Figure 8 The device structure shown in the figure does not constitute a limitation on the electronic device, except Figure 8In addition to the components shown, the electronic device may include more or fewer components than shown, or combine certain components, or arrange the components differently. The electronic device provided in this embodiment can execute the method for managing items in a warehouse provided in the above method embodiment, and its implementation principle and technical effects are similar to the above method, which will not be described in detail here.

[0134] An embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the various processes of the method for managing items in a warehouse in the above method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0135] The computer readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0136] An embodiment of the present application provides a computer program product, which stores a computer program. When the computer program is executed by a processor, the various processes of the method for managing items in a warehouse in the above method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0137] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media that include computer-usable program code.

[0138] In the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0139] In this application, memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0140] In this application, computer-readable media includes permanent and non-permanent, removable and non-removable storage media. Storage media can be implemented by any method or technology to store information, and the information can be computer-readable instructions, data structures, modules of programs or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0141] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0142] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for managing items in a warehouse, applied to a server, characterized in that: Upon receiving a management request from a first client for a project in a remote warehouse, obtaining projects stored in a plurality of remote warehouses; the plurality of remote warehouses are warehouses corresponding to the development task, and are used to store the projects corresponding to the development task, one remote warehouse stores one project, and the development task is realized when all the projects stored in the plurality of remote warehouses are run; Pushing the projects stored in the multiple remote warehouses to the first client, so that the first client displays the projects stored in the multiple remote warehouses as multiple projects in the local warehouse; After determining that the first client performs a target operation on a target project among multiple projects in the local warehouse, the target project after performing the target operation is synchronized to the corresponding remote warehouse.

2. The management method according to claim 1, characterized in that: The method further comprises: Establishing communication with a plurality of first clients; When a change is detected in an item of any remote repository, the changed item is pushed to all first clients.

3. The management method according to claim 1 or 2, characterized in that: The method further comprises: When detecting that an abnormal item exists in the remote warehouse, an abnormal prompt is pushed to the first client; the abnormal prompt is used to instruct the first client to suspend operations on the abnormal item in the local warehouse; Among them, projects that include at least one of the following will be identified as abnormal projects: the project has unreviewed code; the project has duplicate project tags; the project has unmerged project branches; the unmerged project branches refer to project branches that have been created but have not yet been integrated back into the main project.

4. A method for managing items in a warehouse, applied to a first client, characterized in that: In response to the management operation of the project in the remote warehouse triggered by the user, establish communication with the server and send a management request for the project in the remote warehouse to the server; the remote warehouse is a warehouse corresponding to the development task, which is used to store multiple projects corresponding to the development task, and one remote warehouse stores one project; when all the projects stored in the multiple remote warehouses are run, the development task is realized; Receive multiple projects of the remote warehouse pushed by the server, and display the multiple projects as multiple projects of the local warehouse; In response to a target operation triggered by a user on a target project among the multiple projects in the local warehouse, the target operation is performed on the target project, and the target project after the target operation is synchronized to the server.

5. The management method according to claim 4, characterized in that: The method further comprises: Receive a changed project of a remote warehouse pushed from a server, and replace a current project with the changed project; the current project is a project with the same identifier as the changed project among multiple projects in the local warehouse.

6. The management method according to claim 4 or 5, characterized in that: When the target operation is a tag adding operation, in response to the target operation triggered by the user on a target item among the multiple items in the local warehouse, performing the target operation on the target item includes: In response to a tag adding operation triggered by a user for a target project among multiple projects in the local warehouse, displaying a tag information input box; When the tag information input by the user in the tag information input box meets the preset classification, a tag record is generated according to the tag information input by the user and the target project; the tag information is used to identify and\or describe the target project; the classification is the classification corresponding to the target project; the tag record is used to associate the target project with the tag information; When the tag information input by the user in the tag information input box does not satisfy the preset classification, the first prompt information is displayed; the first prompt information is used to prompt the user to re-enter the tag information.

7. The management method according to claim 4 or 5, characterized in that: When the target operation is a replacement operation, in response to the target operation triggered by the user on a target item among the multiple items in the local warehouse, performing the target operation on the target item includes: In response to a replacement operation triggered by a user for a target project among the multiple projects in the local warehouse, obtaining a directory structure of the target project, a target path and a source file name input by the user; Read the target file according to the target path; Determine the actual address of the source file in the target project according to the directory structure and the source file name input by the user; The actual address is accessed, and the source file in the actual address is replaced by the target file.

8. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements a method for managing items in a warehouse as described in any one of claims 1 to 3, or implements a method for managing items in a warehouse as described in any one of claims 4 to 7.

9. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the method for managing items in a warehouse as described in any one of claims 1 to 3, or implements the method for managing items in a warehouse as described in any one of claims 4 to 7.

10. A computer program product, characterized in that When the computer program product runs on a computer, the computer is enabled to implement the method for managing items in a warehouse as claimed in any one of claims 1 to 3, or the method for managing items in a warehouse as claimed in any one of claims 4 to 7.

Images