A method for updating a set of code files and a computing device

Abstract

Embodiments of the present application provide a code file set updating method and a computing device. The method comprises: comparing a first version of a code file set and a customized version of the code file set to obtain a plurality of difference files; determining an existence state of the difference files in a second version of the code file set according to file identifiers and file contents of the difference files; determining modification intentions of the difference files according to modification submission records of the difference files; determining semantic types of the difference files according to the file identifiers of the difference files; determining a difference file processing order according to the existence states of the difference files, the modification intentions of the difference files, and the semantic types of the difference files; and updating the second version of the code file set according to the difference file processing order and the plurality of difference files. The updating reliability of the code file set is improved.

Description

Technical Field

[0001] This application relates to the field of computing device technology, and in particular to a method for updating a code file set and a computing device. Background Technology

[0002] In software development and maintenance, enterprises can perform customized development based on the old baseline code file set (the first version of the code file set) released by the upstream community, forming a customized code file set. When the upstream community develops a new baseline code file set based on the old baseline code file set, the enterprise needs to synchronize (migrate) the modifications made to the customized code file set relative to the old baseline code file set to the new baseline code file set (the second version of the code file set) to complete the update of the new baseline code file set.

[0003] In related technologies, differential analysis tools are typically used to identify multiple difference files between the customized code file set and the old baseline code file set. These multiple difference files are then directly synchronized to the new baseline code file set. This results in critical difference files not taking effect in a timely manner, leading to poor update reliability in the methods used in these technologies. Summary of the Invention

[0004] This application provides a method and computing device for updating a code file set, which can improve the reliability of determining the processing order of difference files, thereby improving the reliability of updating the code file set.

[0005] In a first aspect, embodiments of this application provide a method for updating a set of code files, including:

[0006] The code file set of the first version and the customized version were compared to obtain multiple difference files;

[0007] Based on the file identifier and file content of the difference file, determine the existence status of the difference file in the code file set of the second version;

[0008] Based on the modification and commit history of the difference files, determine the intent behind the modifications.

[0009] Determine the semantic type of the difference file based on its file identifier;

[0010] The processing order of multiple difference files is determined based on their existence status, modification intent, and semantic type.

[0011] The code file set for the second version is updated based on the order in which the difference files are processed and the number of difference files.

[0012] In this scheme, after obtaining multiple difference files by comparing the first version of the code file set and the customized version of the code file set, the computing device can obtain the existence status of the difference files in the second version of the code file set, the modification intent of the difference files, and the semantic type of the difference files. Based on the above three dimensions of information, the computing device determines the processing order of the difference files (indicating the processing order of multiple difference files), so that the processing order of the difference files matches the actual situation (existence status, modification intent, semantic type) of the multiple difference files. This allows the computing device to prioritize the migration of difference files with high migration value and high migration urgency, thereby making the difference files with high migration value and high migration urgency effective in a timely manner. This improves the update reliability of the second version of the code file set, thereby improving the security and reliability of the second version of the code file set and the user experience of the software corresponding to the second version of the code file set.

[0013] In one implementation, the existence status of the difference file in the second version's code file set is determined based on the file identifier and file content of the difference file, including:

[0014] Get the file path of the difference file;

[0015] Based on the file path of the difference file, obtain the file identifier and file content of the difference file;

[0016] The existence status of the difference file is determined based on its file path, file identifier, and file content.

[0017] In this scheme, the computing device can obtain the file identifier and content of the difference file based on its file path. The computing device can then determine the existence status of the difference file based on its file path, file identifier, and content. This method improves the accuracy of determining the existence status.

[0018] In one implementation, the second version's code file set includes multiple candidate files; the existence status of the difference files is determined based on their file paths, file identifiers, and file contents, including:

[0019] Get the file path of the candidate file;

[0020] Based on the file path of the candidate file, obtain the file identifier and file content of the candidate file;

[0021] Based on the file path of the difference file, determine whether the target file exists among multiple candidate files; the file path of the target file matches the file path of the difference file.

[0022] If the existence of the target file is confirmed, the existence status of the difference file is determined based on the file identifier of the difference file, the file content of the difference file, the file identifier of the target file, and the file content of the target file; or,

[0023] If the target file is determined not to exist, the existence status of the difference file is determined based on the file identifier of the difference file, the content of the difference file, the file identifier of each candidate file, and the content of each candidate file.

[0024] In this scheme, when the target file exists among multiple candidate files, the computing device can compare the target file with the difference file individually to determine the presence status of the difference file, thus improving the accuracy of determining its presence status. When the target file does not exist among multiple candidate files, the computing device can improve the accuracy of determining the presence status of the difference file by comparing the difference file sequentially with each candidate file.

[0025] In one implementation, the intent behind the changes in the difference file is determined based on the change commit history, including:

[0026] Retrieve keywords from modification submission records;

[0027] Based on the keywords, query the correspondence between the keywords and the modification intent to determine the modification intent of the difference documents.

[0028] In this scheme, the computing device can determine the modification intent of the difference file by querying the correspondence between keywords and modification intents in the modification submission record. This improves the accuracy of determining the modification intent of the difference file, thereby increasing the accuracy of determining the processing order of the difference file based on the modification intent, and ultimately improving the reliability of the update.

[0029] In one implementation, the semantic type of the difference file is determined based on its file identifier, including:

[0030] Based on the file extension in the file identifier, query the correspondence between file extensions and semantic types to determine the semantic type of the differing files; or...

[0031] Based on the file name in the file identifier, determine the file name characteristics, and based on the file name characteristics, query the correspondence between the file name characteristics and the semantic type to determine the semantic type of the different files.

[0032] In this scheme, the computing device can determine the semantic type of the difference file based on the file extension or file name characteristics (used to indicate the business type of the difference file, and thus to indicate the business importance of the difference file), which improves the accuracy of determining the semantic type of the difference file, thereby improving the accuracy of determining the processing order of the difference file based on the semantic type, and thus improving the reliability of the update.

[0033] In one implementation, the processing order of multiple difference files is determined based on their existence status, modification intent, and semantic type, including:

[0034] For any discrepancy file, determine the score corresponding to the existence status based on the existence status of the discrepancy file;

[0035] Determine the score corresponding to the modification intent based on the modification intent of the discrepancy document;

[0036] Determine the score corresponding to the semantic type based on the semantic type of the difference file;

[0037] The priority score of the difference file is determined based on the score corresponding to the existence state, the score corresponding to the modification intention, and the score corresponding to the semantic type.

[0038] The order in which the difference files are processed is determined based on their priority scores.

[0039] This scheme obtains priority scores for difference files by integrating scores from three dimensions: semantic type, modification intent, and existence status. The processing order of difference files is then determined based on these priority scores, which improves the accuracy of determining the processing order. This ensures that the processing order matches the actual situation of multiple difference files, allowing computing devices to prioritize the migration of difference files with higher priority scores. This improves the update reliability of the second version of the code file set, thereby enhancing its security and reliability.

[0040] In one implementation, the second version's code file set is updated according to the order in which the difference files are processed, and based on multiple difference files, including:

[0041] The risk level of the difference documents is determined based on their priority scores.

[0042] The code file set for version 2 is updated based on the order of processing the difference files, the risk level of multiple difference files, and the number of difference files.

[0043] In this scheme, the computing device can determine the risk level of a difference file based on its priority score. The computing device can then update the second version of the code file set based on the processing order of the difference files, the risk levels of multiple difference files, and the number of difference files themselves. By determining the risk level based on priority scores and then processing the difference files accordingly, the security of difference file processing can be improved.

[0044] In one implementation, the second version of the code file set is updated based on the processing order, the risk level of multiple difference files, and the number of difference files, including:

[0045] Obtain prompts for multiple difference files; the prompts include existence status, modification intent, semantic type, and priority score.

[0046] Obtain review suggestion information for multiple discrepancy files;

[0047] For any discrepancy file, if it is determined that the current processing sequence number is consistent with the processing sequence number of the discrepancy file indicated by the discrepancy file processing order, and the risk level of the discrepancy file is an emergency risk level, the corresponding prompt information and the corresponding audit suggestion information of the discrepancy file are sent to the terminal device.

[0048] Obtain the review result information sent by the terminal device;

[0049] If the audit results indicate that the difference file has passed the audit, the code file set for the second version will be updated according to the difference file.

[0050] In this scheme, if the computing device determines that the current processing sequence number matches the processing sequence number of the difference file indicated by the difference file processing order, and the risk level of the difference file is urgent, it will send the corresponding prompt information and review suggestion information for the difference file to the terminal device. The computing device can then obtain the review result information sent by the terminal device. If the review result information indicates that the difference file has passed review, the computing device can update the second version of the code file set based on the difference file. Through this method, the user's controllability over the processing of urgent risk level difference files is achieved, thereby improving the processing accuracy of urgent risk level difference files and ultimately improving the update accuracy of the code file set.

[0051] In one implementation, the review suggestion information corresponding to multiple difference files is obtained, including:

[0052] Based on the risk level of the discrepancy document, query the correspondence between the risk level and the audit recommendation information to determine the corresponding audit recommendation information for the discrepancy document.

[0053] In this solution, the computing device can query the correspondence between the risk level and the audit recommendation information based on the risk level of the discrepancy document, thereby determining the corresponding audit recommendation information for the discrepancy document. This improves the accuracy of determining the audit recommendation information corresponding to the discrepancy document.

[0054] Secondly, embodiments of this application provide an apparatus for updating a set of code files, comprising:

[0055] The difference identification module is used to compare the first version of the code file set with the customized version of the code file set to obtain multiple difference files;

[0056] The status matching module is used to determine the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file.

[0057] The intent analysis module is used to determine the intent behind the changes made to the difference file based on the change commit history of the difference file.

[0058] The semantic classification module is used to determine the semantic type of the difference files based on their file identifiers.

[0059] The calculation module is used to determine the processing order of multiple difference files based on their existence status, modification intent, and semantic type.

[0060] The update module is used to update the second version of the code file set according to the order of diff file processing and multiple diff files.

[0061] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0062] In one implementation, the state matching module is specifically used for:

[0063] Get the file path of the difference file;

[0064] Based on the file path of the difference file, obtain the file identifier and file content of the difference file;

[0065] The existence status of the difference file is determined based on its file path, file identifier, and file content.

[0066] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0067] In one implementation, the state matching module is specifically used for:

[0068] Get the file path of the candidate file;

[0069] Based on the file path of the candidate file, obtain the file identifier and file content of the candidate file;

[0070] Based on the file path of the difference file, determine whether the target file exists among multiple candidate files; the file path of the target file matches the file path of the difference file.

[0071] If the existence of the target file is confirmed, the existence status of the difference file is determined based on the file identifier of the difference file, the file content of the difference file, the file identifier of the target file, and the file content of the target file; or,

[0072] If the target file is determined not to exist, the existence status of the difference file is determined based on the file identifier of the difference file, the content of the difference file, the file identifier of each candidate file, and the content of each candidate file.

[0073] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0074] In one implementation, the intent analysis module is specifically used for:

[0075] Retrieve keywords from modification submission records;

[0076] Based on the keywords, query the correspondence between the keywords and the modification intent to determine the modification intent of the difference documents.

[0077] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0078] In one implementation, the semantic classification module is specifically used for:

[0079] Based on the file extension in the file identifier, query the correspondence between file extensions and semantic types to determine the semantic type of the differing files; or...

[0080] Based on the file name in the file identifier, determine the file name characteristics, and based on the file name characteristics, query the correspondence between the file name characteristics and the semantic type to determine the semantic type of the different files.

[0081] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0082] In one implementation, the computation module is specifically used for:

[0083] For any discrepancy file, determine the score corresponding to the existence status based on the existence status of the discrepancy file;

[0084] Determine the score corresponding to the modification intent based on the modification intent of the discrepancy document;

[0085] Determine the score corresponding to the semantic type based on the semantic type of the difference file;

[0086] The priority score of the difference file is determined based on the score corresponding to the existence state, the score corresponding to the modification intention, and the score corresponding to the semantic type.

[0087] The order in which the difference files are processed is determined based on their priority scores.

[0088] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0089] In one implementation, the update module is specifically used for:

[0090] The risk level of the difference documents is determined based on their priority scores.

[0091] The code file set for version 2 is updated based on the order of processing the difference files, the risk level of multiple difference files, and the number of difference files.

[0092] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0093] In one implementation, the update module is specifically used for:

[0094] Obtain prompts for multiple difference files; the prompts include existence status, modification intent, semantic type, and priority score.

[0095] Obtain review suggestion information for multiple discrepancy files;

[0096] For any discrepancy file, if it is determined that the current processing sequence number is consistent with the processing sequence number of the discrepancy file indicated by the discrepancy file processing order, and the risk level of the discrepancy file is an emergency risk level, the corresponding prompt information and the corresponding audit suggestion information of the discrepancy file are sent to the terminal device.

[0097] Obtain the review result information sent by the terminal device;

[0098] If the audit results indicate that the difference file has passed the audit, the code file set for the second version will be updated according to the difference file.

[0099] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0100] In one implementation, the update module is specifically used for:

[0101] Based on the risk level of the discrepancy document, query the correspondence between the risk level and the audit recommendation information to determine the corresponding audit recommendation information for the discrepancy document.

[0102] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0103] Thirdly, embodiments of this application provide a computing device, including:

[0104] The processor, and the memory that is in communication with the processor;

[0105] Memory is used to store instructions that the computer executes;

[0106] The processor is used to execute computer execution instructions stored in memory to implement the method of the first aspect.

[0107] The computing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0108] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method of the first aspect.

[0109] When the computer-executable instructions in the computer-readable storage medium provided in this application are executed by a processor, the technical solutions shown in the above method embodiments can be implemented. The implementation principle and beneficial effects are similar, and will not be repeated here.

[0110] Fifthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, is used to implement the method of the first aspect.

[0111] When the computer program in the computer program product provided in this application embodiment is executed by the processor, it can implement the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here. Attached Figure Description

[0112] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0113] Figure 1 A schematic diagram illustrating a method for updating a set of code files provided in an embodiment of this application;

[0114] Figure 2 A flowchart illustrating an embodiment of a method for updating a set of code files provided in this application;

[0115] Figure 3 A flowchart illustrating a second embodiment of a method for updating a code file set provided in this application;

[0116] Figure 4 A flowchart illustrating a third embodiment of a method for updating a code file set provided in this application;

[0117] Figure 5a A schematic diagram illustrating the triggering of updates provided in an embodiment of this application;

[0118] Figure 5b This is a schematic diagram illustrating the display information provided in an embodiment of this application;

[0119] Figure 6 A schematic diagram of a code file set update device provided in an embodiment of this application;

[0120] Figure 7 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Detailed Implementation

[0121] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments made by those skilled in the art under the guidance of these embodiments are within the scope of protection of this application.

[0122] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0123] This application provides a method for updating a code file set. A computing device can compare a first version of the code file set with a customized version to obtain multiple difference files. The computing device can determine the existence status of the difference files in the second version of the code file set based on their file identifiers and contents. The computing device can determine the modification intent of the difference files based on their modification commit records. The computing device can determine the semantic type of the difference files based on their file identifiers. The computing device can determine the processing order of the difference files based on their existence status, modification intent, and semantic type. The computing device can then update the second version of the code file set based on the processing order and the multiple difference files.

[0124] The above method improves the efficiency of determining the processing order of difference files, thereby improving the update efficiency of the code file set.

[0125] The following is a detailed description of the method for updating the code file set according to the embodiments of this application.

[0126] Below, to facilitate understanding of the code file set update method provided in the embodiments of this application, in conjunction with... Figure 1 The application scenarios involved in the embodiments of this application will be introduced.

[0127] Figure 1 This is a schematic diagram illustrating a scenario for updating a code file set, as provided in an embodiment of this application. Figure 1 As shown, the scenario includes a computing device 10 and a terminal device 20.

[0128] The computing device 10 can be a server or a server cluster. When the computing device 10 is a server, from an architectural point of view, the server can be a rack server, a high-density server, a tower server or a full rack server; from a functional point of view, the server can be a general-purpose server or an artificial intelligence server (AI server), for example, an artificial intelligence server can be an image processing server (GPU server).

[0129] Terminal device 20 may be, but is not limited to, various personal computers, laptops, smartphones, and tablets.

[0130] In this scenario:

[0131] Computing device 10 can compare the first version of the code file set with the customized version of the code file set to obtain multiple difference files. In one implementation, computing device 20 receives a processing request sent by terminal device 10. Computing device 20 can respond to the processing request by comparing the first version of the code file set with the customized version of the code file set to obtain multiple difference files.

[0132] The computing device 10 can determine the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file.

[0133] The computing device 10 can determine the modification intent of the difference file based on the modification submission record of the difference file.

[0134] The computing device 10 can determine the semantic type of the difference file based on the file identifier of the difference file.

[0135] The computing device 10 can determine the processing order of multiple difference files based on their existence status, modification intent, and semantic type.

[0136] The computing device 10 can update the second version of the code file set according to the order of processing the difference files and the multiple difference files.

[0137] In another implementation, after updating the second version of the code file set, the computing device can also send prompts and review suggestions for multiple difference files to the terminal device 20. The terminal device 20 can display the prompts and review suggestions for the multiple difference files.

[0138] It should be noted that, Figure 1This is a schematic diagram of a scenario provided in an embodiment of this application. This embodiment of the application does not necessarily represent... Figure 1 The document does not limit the actual form of the various devices included, nor does it specify the form of the devices. Figure 1 The interaction methods between devices are limited, and can be set according to actual needs when applying the solution.

[0139] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0140] Figure 2 This is a flowchart illustrating an embodiment of a method for updating a code file set provided in this application. See also... Figure 2 The method specifically includes the following steps:

[0141] S201: Compare the first version of the code file set with the customized version of the code file set to obtain multiple difference files.

[0142] In this embodiment, the computing device can compare the first version of the code file set and the customized version of the code file set to obtain multiple difference files.

[0143] The first version of the code file set includes multiple first files, while the customized version includes multiple second files. It should be noted that the difference file can be either a first file or a second file.

[0144] It should also be noted that, in one implementation, the first version of the code file set can exist in the form of a code repository. Custom versions of the code file set can also exist in the form of a code repository.

[0145] It should be noted that, in one implementation, the computing device can use multiple threads to compare the first version of the code file set with the customized version of the code file set, and obtain multiple difference files.

[0146] The following describes one implementation method for pre-creating multiple threads in a computing device.

[0147] The computing device can obtain the number of central processing unit (CPU) cores. Based on the number of CPU cores, the computing device can determine the number of threads. Based on the number of threads, the computing device can create multiple threads. It should be noted that the computing device can determine the first value by summing the number of CPU cores with a first preset value. The computing device can determine the number of threads by the smaller of the first value and a second preset value. For example, the first preset value could be 4, and the second preset value could be 32.

[0148] The following section describes one implementation method in which a computing device compares the first version of the code file set with the customized version of the code file set to obtain multiple difference files.

[0149] The computing device can obtain the first directory file of the first version of the code file set. The first directory file includes file identifiers and file paths for multiple first files. The file identifiers include the filename and file extension.

[0150] The computing device can obtain a second directory file containing a customized version of the code file set. This second directory file includes file identifiers and file paths for multiple second files. The file identifiers include the filename and file extension.

[0151] For any given file path, the computing device can determine that the first file corresponding to that file path is a difference file if a first file corresponding to that file path exists in the first version's code file set, and a second file corresponding to that file path does not exist in the customized version's code file set. Alternatively, in one implementation, the computing device can also determine that the event type of the difference file is a deletion type. Furthermore, in another implementation, the computing device can also obtain the structured difference information corresponding to the difference file. It should be noted that when the event type of the difference file is a deletion type, the structured difference information can be the file content of the difference file.

[0152] For any given file path, the computing device can determine that the second file corresponding to that file path is a difference file if a first file corresponding to that file path does not exist in the first version's code file set, but a second file corresponding to that file path exists in the customized version's code file set. Additionally, in one implementation, the computing device can also determine that the event type of the difference file is an "added" type. Furthermore, in another implementation, the computing device can also obtain the structured difference information corresponding to the difference file. It should be noted that when the event type of the difference file is an "added" type, the structured difference information can be the file content of the difference file.

[0153] For any given file path, if a first file corresponding to that file path exists in the first version's code file set, and a second file corresponding to that file path exists in the customized version's code file set, the computing device can determine whether the content of the first file corresponding to that file path is consistent with the content of the second file corresponding to that file path. If the computing device determines that the content of the first file corresponding to that file path is inconsistent with the content of the second file corresponding to that file path, it can determine that the second file corresponding to that file path is a difference file. Additionally, in one implementation, the computing device can also determine that the event type of the difference file is modified. Furthermore, in another implementation, the computing device can also obtain the structured difference information corresponding to the difference file. It should be noted that when the event type of the difference file is modified, the structured difference information can be the difference between the content of the second file and the content of the first file.

[0154] It should be noted that, in one implementation, for any given file path, if a first file corresponding to that file path exists in the first version of the code file set, and a second file corresponding to that file path exists in the customized version of the code file set, the computing device can determine whether the file content size of the first file and the file content size of the second file are both less than or equal to a preset size. For example, the preset size can be 100MB. If the computing device determines that the file content size of both the first and second files is less than or equal to the preset size, it can determine whether the file content of the first file corresponding to that file path is consistent with the file content of the second file corresponding to that file path. If the computing device determines that the file content of the first file corresponding to that file path is inconsistent with the file content of the second file corresponding to that file path, it can determine that the second file corresponding to that file path is a difference file. Additionally, in one implementation, the computing device can also determine that the event type of the difference file is a modification type.

[0155] The following describes one implementation method for a computing device to determine whether the content of the first file corresponding to the file path is consistent with the content of the second file corresponding to the file path.

[0156] In one implementation:

[0157] The computing device can obtain the file types corresponding to the first and second files.

[0158] When the file type is text, the computing device can determine whether the content of the first file is consistent with the content of the second file by comparing them step by step. It should also be noted that during the comparison process, the computing device can ignore differences in blank lines and whitespace.

[0159] When the file type is binary, the computing device can calculate a first checksum based on the content of the first file (e.g., using a hash algorithm). The computing device can calculate a second checksum based on the content of the second file. The computing device can determine whether the first checksum and the second checksum match. If the first checksum and the second checksum match, the computing device can determine that the content of the first file corresponding to that file path matches the content of the second file corresponding to that file path. Alternatively, if the first checksum and the second checksum do not match, the computing device can determine that the content of the first file corresponding to that file path does not match the content of the second file corresponding to that file path.

[0160] S202: Determine the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file.

[0161] In this embodiment, the computing device can determine the existence status (also referred to as the target environment status) of the difference file in the second version of the code file set based on the file identifier and file content of the difference file.

[0162] The following describes one implementation method for a computing device to determine the existence status of a difference file in the second version of the code file set based on the file identifier and file content of the difference file.

[0163] The computing device can obtain the file path of the difference file.

[0164] The computing device can obtain the file identifier and file content of the difference file based on the file path of the difference file.

[0165] The computing device can determine the existence status of a difference file based on its file path, file identifier, and file content.

[0166] The following describes one implementation method for a computing device to determine the existence status of a difference file based on its file path, file identifier, and file content.

[0167] The second version of the code file set includes several candidate files.

[0168] The computing device can obtain the file path of the file to be selected.

[0169] The computing device can obtain the file identifier and file content of the candidate file based on the file path of the candidate file.

[0170] The computing device can determine whether the target file exists among multiple candidate files based on the file path of the difference file. Specifically, the file path of the target file must match the file path of the difference file.

[0171] The computing device can determine the existence status of the difference file based on the file identifier of the difference file, the file content of the difference file, the file identifier of the target file, and the file content of the target file, provided that the target file exists.

[0172] or,

[0173] The computing device can determine the existence status of the difference file based on the file identifier of the difference file, the content of the difference file, the file identifier of each candidate file, and the content of each candidate file, even if it has been determined that the target file does not exist.

[0174] The following describes one implementation method for a computing device to determine the existence status of a difference file based on the file identifier of the difference file, the file content of the difference file, the file identifier of the target file, and the file content of the target file.

[0175] The file identifier includes the filename. That is, the file identifier of the difference file includes the filename of the difference file, and the file identifier of the target file includes the filename of the target file.

[0176] The computing device can determine whether the filename of the difference file matches the filename of the target file.

[0177] If the computing device determines that the filenames of the difference file and the target file are identical, it calculates the content similarity between the difference file and the target file based on their respective content. In one implementation, the computing device can vectorize the content of the difference file to obtain a first vector. The computing device can also vectorize the content of the target file to obtain a second vector. Finally, the computing device can calculate the vector similarity between the first and second vectors and determine this vector similarity as the content similarity between the difference file and the target file.

[0178] The computing device can determine whether the content similarity is greater than or equal to a first similarity threshold. For example, the first similarity threshold could be 0.7.

[0179] The computing device can determine the existence status of the differencing file as a first state if it determines that the content similarity is greater than or equal to a first similarity threshold. It should be noted that the first state refers to the state of existence and no change (exists state). Alternatively, the computing device can determine the existence status of the differencing file as a second state if it determines that the content similarity is less than the first similarity threshold. It should be noted that the second state refers to the state of existence and modification (modified).

[0180] When the computing device determines that the filenames of the difference file and the target file are different, it calculates the content similarity between the difference file and the target file based on the content of the difference file and the target file.

[0181] The computing device can determine whether the content similarity is greater than or equal to a second similarity threshold. For example, the second similarity threshold could be 0.7.

[0182] The computing device can determine the existence status of the differing file as a third state (renamed state) if the content similarity is greater than or equal to a second similarity threshold. It should be noted that the third state refers to the renamed state. Alternatively, the computing device can determine the existence status of the differing file as a fourth state (removed state) if the content similarity is less than the second similarity threshold. It should be noted that the fourth state refers to the state where the file does not exist and there are no similar files.

[0183] The following describes one implementation method for a computing device to determine the existence status of a difference file based on the file identifier of the difference file, the content of the difference file, the file identifier of each candidate file, and the content of each candidate file.

[0184] The file identifier includes the filename. That is, the file identifier of the difference file includes the filename of the difference file, and the file identifier of the candidate file includes the filename of the candidate file.

[0185] The computing device can determine whether a target candidate file exists among multiple candidate files based on the filenames of the difference files, the content of the difference files, the filenames of each candidate file, and the content of each candidate file. Specifically, the filename of the target candidate file must not match the filename of the difference file, and the content similarity between the target candidate file and the difference file must be greater than a third similarity threshold. For example, the third similarity threshold could be 0.7. It should be noted that the content similarity between the target candidate file and the difference file is determined based on the content of both the target candidate file and the difference file.

[0186] The computing device can determine the existence status of the difference file as a third state if it determines that a target candidate file exists. Alternatively, the computing device can determine the existence status of the difference file as a fourth state if it determines that no target candidate file exists.

[0187] S203: Determine the intent behind the changes made to the difference file based on the change commit history of the difference file.

[0188] In this embodiment, the computing device can obtain the modification commit history of the difference file. In one implementation, the modification commit history can be a Git commit history.

[0189] In one implementation, the computing device can determine the total number of modification commit records in the diff file. If the total number is less than a preset number (N), the computing device can retrieve all modification commit records in the diff file. Alternatively, if the total number is greater than or equal to the preset number (N), the computing device can retrieve N modification commit records based on the preset number (N). For example, N can be 10.

[0190] The computing device can determine the intent behind the changes to the difference file based on the change submission history of the difference file.

[0191] The following describes one implementation method for a computing device to determine the modification intent of a difference file based on the modification submission record of the difference file.

[0192] Computing devices can retrieve keywords from modification submission records.

[0193] In one implementation, the computing device can extract keywords from modification submission records based on multiple preset keywords. These keywords are identical to the preset keywords.

[0194] It should be noted that a computing device can acquire one keyword or multiple keywords, and this application embodiment does not limit this.

[0195] Computing devices can store the correspondence between keywords and modification intentions.

[0196] For example, the intent of the modification could be security fix. It's important to note that a security fix refers to eliminating software security vulnerabilities to prevent attacks or data breaches.

[0197] For another example, the intention to modify the software could be to fix a defect. It should be noted that defect fixing refers to correcting errors or anomalies in the software to restore its intended functionality.

[0198] For another example, the intention behind the modification could be performance optimization. It's important to note that performance optimization refers to improving software efficiency or resource utilization without altering functionality.

[0199] For another example, the intention behind the modification could be code refactoring. It should be noted that code refactoring refers to adjusting the internal structure of the code to improve readability and maintainability.

[0200] For another example, the intention to modify the software could be to add new features. It should be noted that new features refer to adding characteristics or capabilities that the software did not previously possess, thereby expanding the software's usability.

[0201] For another example, the intention to modify could be to update a document. It's important to note that updating a document refers to modifying the document itself.

[0202] The computing device can determine the modification intent of the difference file by querying the correspondence between keywords and modification intents.

[0203] It should be noted that a computing device may determine one or more modification intentions, and this application embodiment does not limit this.

[0204] It should also be noted that the modification intent can be called the development intent or the intent tag, and this application embodiment does not limit it.

[0205] S204: Determine the semantic type of the difference file based on its file identifier.

[0206] In this embodiment, the computing device can determine the semantic type of the difference file based on its file identifier. For example, the semantic type could be a business logic file. Another example is a dependency management file. Yet another example is a configuration file.

[0207] The following describes one implementation method for a computing device to determine the semantic type of a difference file based on its file identifier.

[0208] File identifiers can include file extensions.

[0209] Computing devices can store the mapping between file extensions and semantic types. In one implementation, this mapping can be recorded in a file classification dictionary. In another implementation, the mapping can be hard-coded and recorded in the file classification dictionary.

[0210] The computing device can determine the semantic type of the differing file by querying the correspondence between the file extension and the semantic type based on the file extension in the file identifier.

[0211] The following describes another implementation method for a computing device to determine the semantic type of a difference file based on its file identifier.

[0212] File identifiers can include filenames.

[0213] The computing device can store the correspondence between filename features and semantic types. In one implementation, the correspondence between filename features and semantic types can be recorded in a file classification dictionary. In another implementation, the correspondence between filename features and semantic types can be hard-coded and recorded in the file classification dictionary.

[0214] A computing device can determine filename characteristics based on the filename in the file identifier. In one implementation, the computing device can extract filename characteristics from multiple preset filename characteristics. These filename characteristics are identical to the preset filename characteristics.

[0215] The computing device can determine the semantic type of the differing files by querying the correspondence between file name characteristics and semantic types based on file name characteristics.

[0216] In another implementation, the computing device can determine the semantic type of the difference file based on the file identifier and file content of the difference file, using a large language model.

[0217] S205: Determine the processing order of multiple difference files based on their existence status, modification intent, and semantic type.

[0218] In this embodiment, the computing device can determine the processing order of multiple difference files based on their existence status, modification intent, and semantic type.

[0219] The following describes one implementation method for a computing device to determine the processing order of multiple difference files based on their existence status, modification intent, and semantic type.

[0220] For any discrepancy file, the computing device can determine the score corresponding to the existence status based on the existence status of the discrepancy file.

[0221] The computing device can determine the score corresponding to the modification intent based on the modification intent of the difference file.

[0222] The computing device can determine the score corresponding to the semantic type based on the semantic type of the difference file.

[0223] The computing device can determine the priority score of the difference file based on the score corresponding to its existence state, the score corresponding to its modification intent, and the score corresponding to its semantic type. Alternatively, in one implementation, the computing device can also analyze the difference file using analysis tools to obtain its security vulnerability level. The computing device can then determine the score corresponding to the security vulnerability level. Finally, the computing device can determine the priority score of the difference file based on the score corresponding to its existence state, the score corresponding to its modification intent, the score corresponding to its semantic type, and the score corresponding to its security vulnerability level.

[0224] The computing device can determine the processing order of multiple difference files based on their priority scores. The processing order indicates the sequence number of each difference file.

[0225] The following describes another implementation method for determining the processing order of multiple difference files based on their existence status, modification intent, and semantic type.

[0226] The computing device can analyze the existence status of multiple difference files, the modification intent of multiple difference files, and the semantic type of multiple difference files based on a large language model to obtain the processing order of the difference files.

[0227] In another implementation, the computing device can also analyze the processing order of the difference files based on a large language model to obtain risk information. This risk information indicates whether there is a risk in the processing order of the difference files.

[0228] S206: Update the second version of the code file set according to the order of processing the difference files and the number of difference files.

[0229] In this embodiment, the computing device can update the second version of the code file set according to the processing order of the difference files and multiple difference files. That is, the computing device can update the second version of the code file set sequentially based on multiple difference files, according to the processing order of the difference files.

[0230] In one implementation, for any difference file, the computing device can update the second version of the code file set based on the difference file, provided that the current processing sequence number matches the processing sequence number of the difference file indicated by the processing order of the difference file. It should be noted that, in one implementation, the computing device can update the second version of the code file set based on the structured difference information corresponding to the difference file.

[0231] It should be noted that, in one implementation, for any difference file, the computing device can determine whether the existence state of the difference file is in the first state if the current processing sequence number matches the processing sequence number of the difference file indicated by the difference file processing order. If the computing device determines that the existence state of the difference file is in the first state, it can skip the process of updating the second version of the code file set based on the difference file.

[0232] The beneficial effects of this embodiment are as follows: The computing device can compare the first version of the code file set and the customized version of the code file set to obtain multiple difference files. The computing device can determine the existence status of the difference files in the second version of the code file set based on the file information of the difference files; the file information includes file identifiers and file contents. The computing device can determine the modification intent of the difference files based on the modification commit records of the difference files. The computing device can determine the semantic type of the difference files based on the file identifiers of the difference files. The computing device can determine the processing order of the difference files based on the existence status, modification intent, and semantic type of the multiple difference files. The computing device can update the second version of the code file set based on the processing order and the multiple difference files. Through the above methods, the determined processing order of the difference files matches the actual situation of each difference file, thereby improving the reliability of the determined processing order. This allows the computing device to prioritize migrating difference files with high migration value and urgency, thus improving the update reliability of the second version of the code file set, and consequently improving the security and reliability of the second version of the code file set, and ultimately improving the user experience of the software corresponding to the second version of the code file set.

[0233] Figure 3 This is a flowchart illustrating a second embodiment of a method for updating a code library file set, provided as an example of this application. See also... Figure 3 The method specifically includes the following steps:

[0234] S301: Compare the first version of the code file set with the customized version of the code file set to obtain multiple difference files.

[0235] In this embodiment, the computing device can compare the first version of the code file set and the customized version of the code file set to obtain multiple difference files.

[0236] The specific implementation process is the same as that of S201, and will not be described in detail here.

[0237] S302: Determine the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file.

[0238] In this embodiment, the computing device can determine the existence status of the difference file in the second version of the code file set based on the file identifier and file content of the difference file.

[0239] The file information includes the file identifier and the file content.

[0240] The specific implementation process is the same as that of S202, and will not be described in detail here.

[0241] S303: Determine the intent behind the changes made to the difference file based on the change commit history of the difference file.

[0242] In this embodiment, the computing device can determine the modification intent of the difference file based on the modification submission record of the difference file.

[0243] The specific implementation process is the same as that of S203, and will not be described in detail here.

[0244] S304: Determine the semantic type of the difference file based on its file identifier.

[0245] In this embodiment, the computing device can determine the semantic type of the difference file based on the file identifier of the difference file.

[0246] The specific implementation process is the same as that of S204, and will not be described in detail here.

[0247] S305: For any difference file, determine the score corresponding to the existence status based on the existence status of the difference file.

[0248] In this embodiment, for any difference file, the computing device can determine the score corresponding to the existence status based on the existence status of the difference file.

[0249] In one implementation:

[0250] The computing device can store a first correspondence between an existence state and a first score. In one implementation, Table 1 (score table) may include the first correspondence between an existence state and a first score.

[0251] Regarding the existence status (dimension), the computing device can determine whether the first correspondence includes the target first score based on the existence status of the difference file (the dimension value corresponding to the dimension). The target first score corresponds to the existence status of the difference file.

[0252] The computing device can determine the target first score as the score corresponding to the existence state of the difference file if it determines that the first correspondence includes the target first score.

[0253] The computing device can determine the first preset score as the score corresponding to the existence state of the difference file if it determines that the first correspondence does not include the target first score. For example, the first preset score can be 1.

[0254] Table 1. Score Table

[0255]

[0256] S306: Determine the score corresponding to the modification intent based on the modification intent in the difference document.

[0257] In this embodiment, the computing device can determine the score corresponding to the modification intention based on the modification intention of the difference file.

[0258] In one implementation:

[0259] The computing device can store a second correspondence between the modification intention and the second score. In one implementation, Table 1 (score table) may include the second correspondence between the modification intention and the second score.

[0260] Regarding the modification intent (dimension), the computing device can determine whether the second correspondence includes the target second score based on the modification intent (dimension value corresponding to the dimension) of the difference file. The target second score corresponds to the modification intent of the difference file.

[0261] The computing device can determine that the target second score is the score corresponding to the modification intent of the difference document if it determines that the second correspondence includes the target second score.

[0262] The computing device can determine the second preset score as the score corresponding to the modification intent of the difference document if it determines that the second correspondence does not include the target second score. For example, the second preset score can be 0.

[0263] S307: Determine the score corresponding to the semantic type based on the semantic type of the difference file.

[0264] In this embodiment, the computing device can determine the score corresponding to the semantic type based on the semantic type of the difference file.

[0265] In one implementation:

[0266] The computing device can store a third correspondence between semantic types and third fractions. In one implementation, Table 1 (fraction table) may include a third correspondence between semantic types and third fractions.

[0267] Regarding semantic type (dimension), the computing device can determine whether the third correspondence includes the target third score based on the semantic type (dimension value corresponding to the dimension) of the difference file. The target third score corresponds to the semantic type of the difference file.

[0268] If the computing device determines that the third correspondence includes the target third score, it can identify the target third score as the score corresponding to the semantic type of the difference file.

[0269] The computing device can determine the third preset score as the score corresponding to the semantic type of the difference file if it determines that the third correspondence does not include the target third score. For example, the third preset score can be 1.

[0270] S308: Determine the priority score of the difference file based on the score corresponding to the existence state, the score corresponding to the modification intent, and the score corresponding to the semantic type.

[0271] In this embodiment, the computing device can determine the priority score of the difference file based on the score corresponding to the existence state, the score corresponding to the modification intention, and the score corresponding to the semantic type.

[0272] In one implementation:

[0273] In the presence of at least one intention to modify, the computing device can calculate the average of the scores corresponding to at least one intention to modify, and obtain a first score.

[0274] The computing device can obtain a baseline score. For example, the baseline score can be 1. By setting the baseline score, the differences between the files can be made comparable.

[0275] The computing device sums the base score, the score corresponding to the existence state, the first score, and the score corresponding to the semantic type to obtain the priority score of the difference file. For example, Table 2 is a priority score table.

[0276] Table 2 Priority Score Table

[0277]

[0278] Here, A refers to the first version of the code file set, A+ refers to the customized version of the code file set, and B refers to the second version of the code file set.

[0279] S309: Determine the processing order of difference files based on the priority scores of multiple difference files.

[0280] In this embodiment, the computing device can determine the processing order of the difference files based on the priority scores of multiple difference files.

[0281] In one implementation, the computing device can sort multiple difference files according to their priority scores, in descending order of scores, to obtain the processing order of the difference files.

[0282] The processing order of the difference files indicates the processing sequence number of multiple difference files.

[0283] S310: Update the second version's code file set according to the order of processing the difference files and the number of difference files.

[0284] In this embodiment, the computing device can update the second version of the code file set according to the processing order of the difference files and the multiple difference files.

[0285] The specific implementation process is the same as that of S206, and will not be described in detail here.

[0286] The beneficial effects of this embodiment are as follows: In this embodiment, for any difference file, the computing device can determine the score corresponding to the existence status based on the existence status of the difference file. The computing device can determine the score corresponding to the modification intention based on the modification intention of the difference file. The computing device can determine the score corresponding to the semantic type based on the semantic type of the difference file. The computing device can determine the priority score of the difference file based on the score corresponding to the existence status, the score corresponding to the modification intention, and the score corresponding to the semantic type. The computing device can determine the processing order of the difference files based on the priority scores of multiple difference files; the processing order of the difference files indicates the processing sequence number of multiple difference files. By fusing the scores of the three dimensions of semantic type, modification intention, and existence status to obtain the priority score of the difference file, and then determining the processing order of the difference files based on the priority score, the processing order of the difference files matches the actual situation of multiple difference files. This allows the computing device to prioritize the migration of difference files with high migration value and high migration urgency, thereby improving the update reliability of the second version of the code file set.

[0287] Figure 4 This is a flowchart illustrating a third embodiment of a method for updating a code file set, provided in this application. See also... Figure 4 The method specifically includes the following steps:

[0288] S401: Compare the first version of the code file set with the customized version of the code file set to obtain multiple difference files.

[0289] In this embodiment, the computing device can compare the first version of the code file set and the customized version of the code file set to obtain multiple difference files.

[0290] The specific implementation process is the same as that of S201, and will not be described in detail here.

[0291] S402: Determine the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file.

[0292] In this embodiment, the computing device can determine the existence status of the difference file in the second version of the code file set based on the file identifier and file content of the difference file.

[0293] The specific implementation process is the same as that of S202, and will not be described in detail here.

[0294] S403: Determine the intent behind the changes made to the difference file based on the change commit history of the difference file.

[0295] In this embodiment, the computing device can determine the modification intent of the difference file based on the modification submission record of the difference file.

[0296] The specific implementation process is the same as that of S203, and will not be described in detail here.

[0297] S404: Determine the semantic type of the difference file based on its file identifier.

[0298] In this embodiment, the computing device can determine the semantic type of the difference file based on the file identifier of the difference file.

[0299] The specific implementation process is the same as that of S204, and will not be described in detail here.

[0300] S405: For any difference file, determine the score corresponding to the existence status based on the existence status of the difference file.

[0301] In this embodiment, for any difference file, the computing device can determine the score corresponding to the existence status based on the existence status of the difference file.

[0302] The specific implementation process is the same as that of S305, and will not be described in detail here.

[0303] S406: Determine the score corresponding to the modification intent based on the modification intent in the difference document.

[0304] In this embodiment, the computing device can determine the score corresponding to the modification intention based on the modification intention of the difference file.

[0305] The specific implementation process is the same as that of S306, and will not be described in detail here.

[0306] S407: Determine the score corresponding to the semantic type based on the semantic type of the difference file.

[0307] In this embodiment, the computing device can determine the score corresponding to the semantic type based on the semantic type of the difference file.

[0308] The specific implementation process is the same as that of S307, and will not be described in detail here.

[0309] S408: Determine the priority score of the difference file based on the score corresponding to the existence state, the score corresponding to the modification intent, and the score corresponding to the semantic type.

[0310] In this embodiment, the computing device can determine the priority score of the difference file based on the score corresponding to the existence state, the score corresponding to the modification intention, and the score corresponding to the semantic type.

[0311] The specific implementation process is the same as that of S308, and will not be described in detail here.

[0312] S409: Determine the processing order of difference files based on the priority scores of multiple difference files.

[0313] In this embodiment, the computing device can determine the processing order of the difference files based on the priority scores of multiple difference files.

[0314] The processing order of the difference files indicates the processing sequence number of multiple difference files.

[0315] The specific implementation process is the same as that of S309, and will not be described in detail here.

[0316] S410: Determine the risk level of the difference file based on its priority score.

[0317] In this embodiment, the computing device can determine the risk level of a difference file based on its priority score.

[0318] The following describes one implementation method for determining the risk level of a difference file based on its priority score.

[0319] The computing device can store the correspondence between risk levels and priority score ranges. In one implementation, Table 3 is a risk level table that records the correspondence between risk levels and priority score ranges.

[0320] The computing device can determine the priority score range to which the priority score of the difference file belongs.

[0321] The computing device can determine the risk level of a difference document by querying the correspondence between the risk level and the priority score range based on the priority score range to which the difference document belongs.

[0322] Table 3 is the risk level table.

[0323]

[0324] S411: Update the second version of the code file set based on the order of processing the difference files, the risk level of multiple difference files, and the number of difference files.

[0325] In this embodiment, the computing device can update the second version of the code file set based on the processing order of the difference files, the risk level of multiple difference files, and the multiple difference files.

[0326] The following describes an implementation method for updating the second version of the code file set by a computing device based on the processing order of the difference files, the risk level of multiple difference files, and the multiple difference files.

[0327] The computing device can obtain prompt information corresponding to multiple difference files. This prompt information may include one or more of the following fields: existence status, modification intent, semantic type, priority score, event type, file path, modification commit record, and risk level.

[0328] The computing device can obtain review recommendation information corresponding to multiple discrepancy documents. In one implementation, the computing device can store the correspondence between risk levels and review recommendations. The computing device can query the correspondence between risk levels and review recommendation information based on the risk level of the discrepancy document to determine the corresponding review recommendation information.

[0329] For any discrepancy file, the computing device, upon determining that the current processing sequence number matches the processing sequence number of the discrepancy file indicated by the discrepancy file processing order, and that the risk level of the discrepancy file is urgent, will send the corresponding prompt information and review suggestion information to the terminal device. Understandably, the terminal device can control the display interface to show the corresponding prompt information and review suggestion information. The terminal device can also obtain user-input review result information through the display interface. It should be noted that the review result information can be input by the user based on the prompt information and review suggestion information displayed on the display interface.

[0330] The computing device can obtain the review result information sent by the terminal device. This review result information can indicate that the discrepancy document has passed review, or it can indicate that the discrepancy document has failed review.

[0331] If the audit result information indicates that the difference file has been approved, the computing device can update the second version of the code file set based on the difference file.

[0332] The beneficial effects of this embodiment are as follows: In this embodiment, the computing device can determine the risk level of a difference file based on its priority score. The computing device can update the second version of the code file set based on the processing order of the difference files, the risk levels of multiple difference files, and the multiple difference files themselves. By determining the risk level based on the priority score and then processing the difference files based on the risk level, the security of difference file processing can be improved.

[0333] Figure 5a This is a schematic diagram illustrating the triggering of updates provided in an embodiment of this application. Figure 5b This is a schematic diagram illustrating the display information provided in an embodiment of this application.

[0334] Below, in conjunction with Figure 5a and Figure 5b The update process of the code file set is explained.

[0335] In one implementation:

[0336] Terminal devices can display a visual interface.

[0337] Terminal devices can respond to user actions on the visual interface and obtain update tasks.

[0338] The update task can specify a first version of the code file set, a customized version of the code file set, and a second version of the code file set. For example, such as... Figure 5a As shown, the update task may include an identifier for the first version of the code file set (code file set 1), an identifier for the customized version of the code file set (code file set 2), and an identifier for the second version of the code file set (code file set 3). Additionally, in one implementation, the update task may also include a task description and a start time.

[0339] Terminal devices can send update tasks to computing devices.

[0340] The computing device can compare the first version of the code file set with a customized version, obtaining multiple difference files. Based on the file identifiers and contents of these difference files, the computing device can determine their existence in the second version of the code file set. Based on the commit history of the difference files, the computing device can determine their modification intent. Based on their file identifiers, the computing device can determine their semantic type. Based on the existence, modification intent, and semantic type of the multiple difference files, the computing device can determine the processing order for these difference files. Based on the processing order and the multiple difference files, the computing device can update the second version of the code file set.

[0341] The computing device can also send prompts and review suggestions for multiple difference files to the terminal device after updating the second version of the code file set according to the processing order of the difference files and multiple difference files.

[0342] The prompt information may include one or more of the following fields: existence status, modification intent, semantic type, priority score, event type, file path, modification commit record, and risk level.

[0343] It should be noted that the fields included in the prompt information may depend on the fields determined by the computing device. For example, regarding S206, if the computing device determines the existence status of the difference file, the modification intent of the difference file, and the semantic type of the difference file, the prompt information may include the existence status, modification intent, and semantic type. As another example, regarding S310, if the computing device determines the existence status of the difference file, the modification intent of the difference file, the semantic type of the difference file, and the priority score of the difference file, the prompt information may include the existence status, modification intent, semantic type, and priority score. As yet another example, regarding S3411, if the computing device determines the existence status of the difference file, the modification intent of the difference file, the semantic type of the difference file, the priority score of the difference file, and the risk level of the difference file, the prompt information may include the existence status, modification intent, semantic type, priority score, and risk level.

[0344] The terminal device can control the display interface to show prompts and review suggestions for multiple discrepancies. For example... Figure 5b As shown, the terminal device can display prompts and review suggestions for multiple difference files. It should also be noted that... Figure 5b The alert information may include the existence status, modification intent, event type, file path, modification commit history, and risk level.

[0345] By displaying prompts and audit suggestions for multiple difference files through the control computing device's interface, users can accurately understand the actual situation of each difference file, thereby achieving auditability of the code file set update process.

[0346] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0347] Figure 6 This is a schematic diagram of a code file set update device provided in an embodiment of this application. Figure 6 As shown, the code file set update device 60 includes a difference recognition module 61, a state matching module 62, an intent analysis module 63, a semantic classification module 64, a calculation module 65, and an update module 66.

[0348] The difference identification module 61 is used to compare the code file set of the first version and the code file set of the customized version to obtain multiple difference files;

[0349] The status matching module 62 is used to determine the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file.

[0350] The intent analysis module 63 is used to determine the intent behind the modification of the difference file based on the modification commit history of the difference file.

[0351] The semantic classification module 64 is used to determine the semantic type of the difference file based on the file identifier of the difference file;

[0352] The calculation module 65 is used to determine the processing order of multiple difference files based on the existence status of multiple difference files, the modification intent of multiple difference files, and the semantic type of multiple difference files.

[0353] Update module 66 is used to update the second version of the code file set according to the order of processing the difference files and multiple difference files.

[0354] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0355] In one implementation, the state matching module 62 is specifically used for:

[0356] Get the file path of the difference file;

[0357] Based on the file path of the difference file, obtain the file identifier and file content of the difference file;

[0358] The existence status of the difference file is determined based on its file path, file identifier, and file content.

[0359] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0360] In one implementation, the second version of the code file set includes multiple candidate files; the state matching module 62 is specifically used for:

[0361] Get the file path of the candidate file;

[0362] Based on the file path of the candidate file, obtain the file identifier and file content of the candidate file;

[0363] Based on the file path of the difference file, determine whether the target file exists among multiple candidate files; the file path of the target file matches the file path of the difference file.

[0364] If the existence of the target file is confirmed, the existence status of the difference file is determined based on the file identifier of the difference file, the file content of the difference file, the file identifier of the target file, and the file content of the target file; or,

[0365] If the target file is determined not to exist, the existence status of the difference file is determined based on the file identifier of the difference file, the content of the difference file, the file identifier of each candidate file, and the content of each candidate file.

[0366] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0367] In one implementation, the intent analysis module 63 is specifically used for:

[0368] Retrieve keywords from modification submission records;

[0369] Based on the keywords, query the correspondence between the keywords and the modification intent to determine the modification intent of the difference documents.

[0370] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0371] In one implementation, the semantic classification module 64 is specifically used for:

[0372] Based on the file extension in the file identifier, query the correspondence between file extensions and semantic types to determine the semantic type of the differing files; or...

[0373] Based on the file name in the file identifier, determine the file name characteristics, and based on the file name characteristics, query the correspondence between the file name characteristics and the semantic type to determine the semantic type of the different files.

[0374] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0375] In one implementation, the calculation module 65 is specifically used for:

[0376] For any discrepancy file, determine the score corresponding to the existence status based on the existence status of the discrepancy file;

[0377] Determine the score corresponding to the modification intent based on the modification intent of the discrepancy document;

[0378] Determine the score corresponding to the semantic type based on the semantic type of the difference file;

[0379] The priority score of the difference file is determined based on the score corresponding to the existence state, the score corresponding to the modification intention, and the score corresponding to the semantic type.

[0380] The order in which the difference files are processed is determined based on their priority scores.

[0381] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0382] In one implementation, update module 66 is specifically used for:

[0383] The risk level of the difference documents is determined based on their priority scores.

[0384] The code file set for version 2 is updated based on the order of processing the difference files, the risk level of multiple difference files, and the number of difference files.

[0385] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0386] In one implementation, update module 66 is specifically used for:

[0387] Obtain prompts for multiple difference files; the prompts include existence status, modification intent, semantic type, and priority score.

[0388] Obtain review suggestion information for multiple discrepancy files;

[0389] For any discrepancy file, if it is determined that the current processing sequence number is consistent with the processing sequence number of the discrepancy file indicated by the discrepancy file processing order, and the risk level of the discrepancy file is an emergency risk level, the corresponding prompt information and the corresponding audit suggestion information of the discrepancy file are sent to the terminal device.

[0390] Obtain the review result information sent by the terminal device;

[0391] If the audit results indicate that the difference file has passed the audit, the code file set for the second version will be updated according to the difference file.

[0392] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0393] In one implementation, update module 66 is specifically used for:

[0394] Based on the risk level of the discrepancy document, query the correspondence between the risk level and the audit recommendation information to determine the corresponding audit recommendation information for the discrepancy document.

[0395] The code file set update device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0396] Figure 7 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Figure 7 As shown, the computing device 70 includes a processor 71 and a memory 72; wherein the processor 71 is coupled to the memory 72, and the memory 72 is used to store computer instructions; the processor 71 is used to execute the computer instructions to cause the computing device 70 to perform the technical solutions in the aforementioned method embodiments.

[0397] Optionally, the memory 72 can be either standalone or integrated with the processor 71. Optionally, when the memory 72 is a device independent of the processor 71, the computing device 70 may further include a bus 73 for connecting the aforementioned devices.

[0398] The processor is used to execute the technical solutions in the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0399] This application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the technical solutions provided in the aforementioned method embodiments.

[0400] This application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions provided in the aforementioned method embodiments.

[0401] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as volatile memory and non-volatile memory.

[0402] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for updating a set of code files, characterized in that, include: The code file set of the first version and the customized version were compared to obtain multiple difference files; Based on the file identifier and file content of the difference file, determine the existence status of the difference file in the code file set of the second version; Based on the modification commit history of the difference file, determine the modification intent of the difference file; The semantic type of the difference file is determined based on its file identifier. The processing order of multiple difference files is determined based on their existence status, modification intent, and semantic type. The code file set of the second version is updated according to the order of processing the difference files and the number of difference files.

2. The method according to claim 1, characterized in that, The step of determining the existence status of the difference file in the second version's code file set based on the file identifier and file content of the difference file includes: Obtain the file path of the difference file; Based on the file path of the difference file, obtain the file identifier and file content of the difference file; The existence status of the difference file is determined based on its file path, file identifier, and file content.

3. The method according to claim 2, characterized in that, The second version of the code file set includes multiple candidate files; determining the existence status of the difference file based on its file path, file identifier, and content includes: Obtain the file path of the candidate file; Based on the file path of the candidate file, obtain the file identifier and file content of the candidate file; Based on the file path of the difference file, determine whether the target file exists among multiple candidate files; the file path of the target file matches the file path of the difference file. If the existence of the target file is determined, the existence status of the difference file is determined based on the file identifier of the difference file, the file content of the difference file, the file identifier of the target file, and the file content of the target file; or, If it is determined that the target file does not exist, the existence status of the difference file is determined based on the file identifier of the difference file, the content of the difference file, the file identifier of each candidate file, and the content of each candidate file.

4. The method according to any one of claims 1-3, characterized in that, Determining the modification intent of the difference file based on the modification commit history of the difference file includes: Obtain the keywords from the modification submission record; Based on the keywords, query the correspondence between the keywords and the modification intent to determine the modification intent of the difference file.

5. The method according to any one of claims 1-4, characterized in that, Determining the semantic type of the difference file based on its file identifier includes: Based on the file extension in the file identifier, query the correspondence between the file extension and the semantic type to determine the semantic type of the differing file; or... Based on the file name in the file identifier, determine the file name feature, and based on the file name feature, query the correspondence between the file name feature and the semantic type to determine the semantic type of the differential file.

6. The method according to any one of claims 1-5, characterized in that, The step of determining the processing order of multiple difference files based on their existence status, modification intent, and semantic type includes: For any discrepancy file, determine the score corresponding to the existence status based on the existence status of the discrepancy file; Based on the modification intent of the difference file, determine the score corresponding to the modification intent; Based on the semantic type of the difference file, determine the score corresponding to the semantic type; The priority score of the difference file is determined based on the score corresponding to the existence state, the score corresponding to the modification intention, and the score corresponding to the semantic type. The processing order of the difference files is determined based on the priority scores of multiple difference files.

7. The method according to claim 6, characterized in that, The step of updating the code file set of the second version according to the processing order of the difference files and multiple difference files includes: The risk level of the difference file is determined based on its priority score. The code file set of the second version is updated based on the processing order of the difference files, the risk level of multiple difference files, and the multiple difference files.

8. The method according to claim 7, characterized in that, The step of updating the code file set of the second version according to the processing order of the difference files, the risk level of multiple difference files, and the multiple difference files includes: Obtain prompt information corresponding to multiple difference files; the prompt information includes existence status, modification intent, semantic type, and priority score; Obtain review suggestion information for multiple discrepancy files; For any discrepancy file, if it is determined that the current processing sequence number is consistent with the processing sequence number of the discrepancy file indicated by the processing order of the discrepancy file, and the risk level of the discrepancy file is an emergency risk level, the corresponding prompt information and the corresponding review suggestion information of the discrepancy file are sent to the terminal device. Obtain the review result information sent by the terminal device; If the audit result information indicates that the difference file has passed the audit, the code file set of the second version shall be updated according to the difference file.

9. The method according to claim 8, characterized in that, The step of obtaining review suggestion information corresponding to multiple difference files includes: Based on the risk level of the difference document, query the correspondence between the risk level and the audit recommendation information to determine the audit recommendation information corresponding to the difference document.

10. A computing device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory is used to store computer-executed instructions; The processor is configured to execute computer execution instructions stored in the memory to implement the method according to any one of claims 1-9.

Images