CN116932040A

CN116932040A - Query method, device, equipment and storage medium of source code

Info

Publication number: CN116932040A
Application number: CN202311002349.4A
Authority: CN
Inventors: 朱家伟
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-08-09
Filing date: 2023-08-09
Publication date: 2023-10-24

Abstract

The application provides a source code query method, a source code query device, source code query equipment and a source code query storage medium, and relates to the field of financial science and technology or other related fields. The method comprises the following steps: in response to receiving a request for acquiring the requirement item information, invoking a first query interface to access a requirement item management system to acquire the requirement item information, and/or in response to receiving a request for acquiring the program problem information, invoking a second query interface to access a program problem management system to acquire the program problem information; according to a preset format, carrying out format conversion on the requirement item information and/or the program problem information to obtain submitted information; and inquiring source codes corresponding to the requirement item information and/or the program problem information according to the submitted information. The method of the application can realize the effective inquiry of the source code.

Description

Query method, device, equipment and storage medium of source code

Technical Field

The present application relates to the field of financial technology or other related fields, and in particular, to a method, an apparatus, a device, and a storage medium for querying a source code.

Background

Source code management refers to managing code for multiple developer projects. The developers can cooperatively process the codes of the multi-developer engineering through source code management and track changes so as to protect the source codes of the multi-developer engineering from being influenced by disaster difficulty, personal errors and accidental degradation caused by unexpected results.

In the related art, when the source code query of the multi-developer project is implemented, it is usually required to rely on the Git tool, that is, all history records of the source code of the multi-developer project can be queried through the Git tool, but when the source code of the multi-developer project is queried through the Git tool, the query is typically performed through default information of the Git tool, such as author, submission time, information of branches to which the code belongs, etc., and if the default information of the Git tool does not exist, the query cannot be implemented on the source code of the multi-developer project.

Thus, there is a need for a solution that can enable efficient querying of source code.

Disclosure of Invention

The application provides a source code query method, a device, equipment and a storage medium, which are used for realizing effective query of source codes.

In a first aspect, the present application provides a source code query method, applied to a Git graphic client, where the Git graphic client accesses a requirement item management system by calling a first query interface, and the Git graphic client accesses a program problem management system by calling a second query interface, where the requirement item management system is used for storing requirement item information of a target software project, and the program problem management system is used for storing program problem information of the target software project; the query method comprises the following steps: in response to receiving a request for acquiring the requirement item information, invoking a first query interface to access a requirement item management system to acquire the requirement item information, and/or in response to receiving a request for acquiring the program problem information, invoking a second query interface to access a program problem management system to acquire the program problem information; according to a preset format, carrying out format conversion on the requirement item information and/or the program problem information to obtain submitted information; and inquiring source codes corresponding to the requirement item information and/or the program problem information according to the submitted information.

In a second aspect, the present application provides a query device for source code, which is applied to a Git graphical client, where the Git graphical client accesses a requirement item management system by calling a first query interface, and the Git graphical client accesses a program problem management system by calling a second query interface, where the requirement item management system is used for storing requirement item information of a target software project, and the program problem management system is used for storing program problem information of the target software project; the query device of the source code comprises: the system comprises an acquisition module, a program problem management system and a program problem management system, wherein the acquisition module is used for calling a first query interface to access the program problem management system in response to receiving a request for acquiring the information of the requirement item, and/or calling a second query interface to access the program problem management system in response to receiving the request for acquiring the information of the program problem, and acquiring the information of the program problem; the format conversion module is used for carrying out format conversion on the requirement item information and/or the program problem information according to a preset format to obtain submitted information; and the query module is used for querying source codes corresponding to the requirement item information and/or the program problem information according to the submitted information.

In a third aspect, the present application provides an electronic device comprising: a processor and a memory coupled to the processor; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to implement the method of querying the source code of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed, are adapted to carry out a method of querying source code as in the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which when executed implements the method of querying source code of the first aspect.

According to the query method, the query device, the query equipment and the query storage medium for the source code, the functions of the access requirement item management system and the program problem management system are added in the Git graphical client, so that when the requirement item information and/or the program problem information need to be acquired, the corresponding access interface is called to access the requirement item management system and/or the program problem management system so as to acquire the requirement item information and/or the program problem information, the requirement item information and/or the program problem information do not need to be manually input, and the efficiency and the accuracy for acquiring the requirement item information and/or the program problem information are improved; and format conversion processing can be performed on the requirement item information and/or the program problem information according to a preset format, so that the obtained submitted information is unified in format, analysis and calculation are conveniently performed on the submitted information in the unified format in the follow-up process, and the source code of the target software engineering can be quickly and effectively inquired through the requirement item information and/or the program problem information.

Drawings

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

FIG. 1 is a schematic diagram of a source code query system according to an embodiment of the present application;

FIG. 2 is a flow chart of a source code query method according to an embodiment of the present application;

FIG. 3 is an interface schematic diagram of a graphical interface of a Git graphical client according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an interface for querying information about a demand item according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a source code query device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

It should be noted that the method, the device, the equipment and the storage medium for querying the source code of the present application may be used in the field of finance technology or other related fields, and may also be used in any field other than the field of finance technology or other related fields.

First, the terms involved in the present application will be explained:

source code: may also be referred to as a source program, meaning an uncompiled text file written in accordance with a certain programming language specification.

Git: an open-source distributed version control system can efficiently and rapidly handle version management of software projects from very small to very large.

The demand item: business requirement unit reached by software engineering development.

Program problem: problems that the program generates after the software engineering is developed.

Commit Message (Commit Message): the Git tool requires text information entered by the developer when submitting the code.

In the related art provided in the background art, at least the following technical problems exist:

currently, the industry widely uses a Git tool to perform source code management of software engineering, and all histories of source code can be queried through the Git tool, and the manner of querying the histories is generally related to the Git tool itself, such as author, submission time, branches to which the source code belongs, and the like. However, during the period of software engineering, it may be necessary to trace back relevant source code by business meaning, for example, by demand terms or program problems, in which case the default Git tool itself is difficult to query for relevant source code.

Aiming at the problems in the related art, the application provides a query method of source codes, which adds the functions of an access requirement item management system and a program problem management system in a Git graphical client, so that when the requirement item information and/or the program problem information need to be acquired, the requirement item management system and/or the program problem management system can be accessed by calling a corresponding access interface, and the requirement item information and/or the program problem information need to be obtained by adopting a predetermined query condition query without manually inputting the requirement item information and/or the program problem information, thereby improving the efficiency and the accuracy of acquiring the requirement item information and/or the program problem information; and format conversion processing can be performed on the requirement item information and/or the program problem information according to a preset format, so that the obtained submitted information is unified in format, analysis and calculation are conveniently performed on the submitted information in the unified format in the follow-up process, and the source code of the target software engineering can be quickly and effectively inquired through the requirement item information and/or the program problem information.

In one embodiment, the query method of source code may be applied in an application scenario. Fig. 1 is a schematic structural diagram of a source code query system according to an embodiment of the present application, where, as shown in fig. 1, the source code query system may include a Git graphic client, a Git server, a requirement item management system, and a program problem management system. The system comprises a request item management system, a first query interface and a second query interface, wherein the request item management system stores request item information of target software engineering and provides a first query interface for a Git graphical client to access; program problem information of the target software engineering is stored in the program problem management system, and a second query interface is provided for the Git graphical client to access.

In this application scenario, related personnel may interact with the Git graphical client through a graphical interface at the Git graphical client. That is, the relevant personnel may operate at the graphical interface to effect sending a request to the Git graphical client to obtain the requirement item information and/or the program issue information to query the requirement item information and/or the program issue information. Specifically, after receiving a request for acquiring the requirement item information, the Git graphical client calls a first query interface to access the requirement item management system, jumps to a requirement item information query interface, selects or inputs a corresponding query condition in the requirement item information query interface, and can query the requirement item information; and after receiving the request for acquiring the program problem information, the Git graphical client calls the second query interface to access the program problem management system, jumps to the program problem information query interface, and related personnel select or input corresponding query conditions in the program problem information query interface so as to query the program problem information. Therefore, the requirement item information and/or the program problem information do not need to be manually input, and the efficiency and the accuracy for acquiring the requirement item information and/or the program problem information are improved.

In the application scenario, after acquiring the requirement item information and/or the program problem information, the Git graphical client may perform format conversion on the requirement item information and/or the program problem information according to a data format corresponding to a preset template, so as to obtain submitted information, and may submit the submitted information to the Git server for storage. Therefore, the method can facilitate the subsequent analysis and calculation of the submitted information in a unified format so as to quickly and effectively query the source code of the target software engineering through the requirement item information and/or the program problem information.

In the application scenario, after the Git graphical client obtains the submitted information, the related source code of the target software project can be queried according to the requirement item information and/or the program problem information with uniform format in the submitted information.

In view of the foregoing, the following detailed description will be given of the technical solution of the present application and how the technical solution of the present application solves the foregoing technical problems with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

The application provides a source code query method, which is applied to a Git graphical client, wherein the Git graphical client accesses a program problem management system by calling a first query interface, the Git graphical client accesses the program problem management system by calling a second query interface, the program problem management system is used for storing the requirement item information of a target software project, and the program problem management system is used for storing the program problem information of the target software project. Fig. 2 is a flow chart of a source code query method according to an embodiment of the present application, as shown in fig. 2, the source code query method includes the following steps:

s201: in response to receiving a request for acquiring the requirement item information, invoking the first query interface to access the requirement item management system, acquiring the requirement item information, and/or in response to receiving a request for acquiring the program problem information, invoking the second query interface to access the program problem management system, and acquiring the program problem information.

In this step, the relevant person may operate at the Git-graphical client such that the Git-graphical client receives a request for obtaining the demand item information and/or a request for obtaining the program issue information.

In an alternative embodiment, in the development process of the target software project, the source code of the target software project can be continuously modified or adjusted according to the collected requirements for the target software project, and the program problem of the target software project is modified, so that specific information of each modification needs to be recorded, corresponding to the modification, and/or program problem information needs to be recorded when each modification is traced, and therefore the requirement information can be stored into a requirement management system for management, and the program problem information is stored into the program problem management system for management.

S202: and carrying out format conversion on the requirement item information and/or the program problem information according to a preset format to obtain the submitted information.

In this step, the preset format may be determined by a preset template of the submitted information, and after the requirement item information and/or the program problem information are obtained, the content of the requirement item information and/or the program problem information may be directly added to the preset template, so as to form submitted information with uniform format. Each commit message may correspond to a modification of source code of a target software project and a commit to be online.

Optionally, since the target software project is a software project cooperatively developed by multiple persons, the requirement item information and the program problem information of the target software project may come from different developers, so that the data formats of the requirement item information and the program problem information may be different, and in order to facilitate the subsequent analysis of the submitted information, the requirement item information and the program problem information may be unified in format.

S203: and inquiring source codes corresponding to the requirement item information and/or the program problem information according to the submitted information.

In this step, the format of the submitted information is fixed and unified, so that the efficiency of analyzing the submitted information can be improved, thereby determining the related data of the requirement item information and/or the program problem information included in the submitted information, and querying the corresponding source code in the target software engineering.

In an alternative embodiment, the queried source code may be displayed in an interface of the Git graphical client and the modified code identified in the displayed source code.

According to the query method of the source code, the functions of the requirement item management system and the program problem management system are added in the Git graphical client, so that when the requirement item information and/or the program problem information need to be acquired, the requirement item management system and/or the program problem management system can be accessed by calling the corresponding access interface to acquire the requirement item information and/or the program problem information, the requirement item information and/or the program problem information do not need to be manually input, and the efficiency and the accuracy for acquiring the requirement item information and/or the program problem information are improved; and format conversion processing can be performed on the requirement item information and/or the program problem information according to a preset format, so that the obtained submitted information is unified in format, analysis and calculation are conveniently performed on the submitted information in the unified format in the follow-up process, and the source code of the target software engineering can be quickly and effectively inquired through the requirement item information and/or the program problem information.

In one embodiment, the Git graphical client provides a graphical interface, invokes a first query interface to access a demand item management system in response to receiving a request to obtain demand item information, obtains demand item information, and/or invokes a second query interface to access a program problem management system in response to receiving a request to obtain program problem information, the obtaining program problem information comprising: in response to receiving a first operation facing a first area on the graphical interface, calling a first query interface to access a demand item management system to acquire demand item information, wherein the first operation generates a request for acquiring the demand item information; and/or, in response to receiving a second operation facing a second area on the graphical interface, invoking a second query interface to access the program problem management system to obtain program problem information, the second operation generating a request for obtaining the program problem information.

In this embodiment, the graphical interface provided by the Git graphical client may be as shown in fig. 3, where the graphical interface includes four main areas, in fig. 3, a first main area, a second main area, a third main area, and a fourth main area. Wherein the first main area displays a catalog of a plurality of sub-items of the target software project; displaying in the second main area a catalog of selected sub-items of the plurality of sub-items displayed in the first main area; displaying source code of the selected sub-item in a third main area; the fourth main area includes a first area in which a "acquire demand item information" button is provided and a second area in which a "acquire program problem information" button is provided.

Specifically, the first operation and the second operation may each be a single click operation, a double click operation, a long press operation, or the like. Taking the first operation and the second operation as single click operations as an example, a related person acquires the requirement item information by clicking a button for acquiring the requirement item information, and acquires the program problem information by clicking a button for acquiring the program problem information. After the first operation facing the first area is received by the Git graphical client, the first query interface can be called to access the requirement item management system to obtain the requirement item information, and/or the second operation facing the second area on the graphical interface is received, and the second query interface is called to access the program problem management system to obtain the program problem information. Therefore, related personnel are not required to manually input the information of the required item and/or the program problem information, the problem that the efficiency is low and the error is prone to occur due to manual input is avoided, and the efficiency and the accuracy of acquiring the information of the required item and/or the program problem information are improved.

Optionally, the fourth main area further includes a submitted information display area, after the requirement item information and/or the program problem information is acquired, submitted information obtained after the requirement item information and/or the program problem information is converted into a format according to a preset format may be displayed in the submitted information display area, for example, in fig. 3, the submitted information may be as follows (only one example):

[ task name ]

[ code branching ]

[ project number ] xxxxxxx

[ project name ] xxxxxxxxxxxxxxxxxx

[ task description ]

Xxx version

**************************************

Optionally, a "submit" button may be further disposed in the submit information display area, after the submit information is displayed in the submit information display area, the submit information may be submitted to the Git server for saving through the "submit" button, so that the source code query may be further improved by directly obtaining the submit information in the Git server for the subsequent query of the source code.

In one embodiment, the requirement item management system provides a requirement item information query interface, and in response to receiving a first operation facing a first area on the graphical interface, calls the first query interface to access the requirement item management system to obtain requirement item information, including: responding to the received first operation facing the first area on the graphical interface, calling a first query interface to access a demand item information query interface, and displaying demand item information query conditions and demand item information in the demand item information query interface; demand item information is received from a demand item management system.

In this embodiment, the requirement item information query interface provided by the requirement item management system may be used for related personnel to query and display requirement item information through requirement item information query conditions. The demand item information query interface provided by the demand item management system may be as shown in fig. 4.

The requirement item information query interface in fig. 4 may include a third area in which requirement item information query conditions may be displayed, and a requirement item information query result display area in which a "search" button and a "ok" button may be provided. After the requirement item information query condition is determined, a related person can click a search button, so that the requirement item information searched by the requirement item information query condition can be displayed in a requirement item information query result display area, the requirement item information displayed in the requirement item information query result display area can comprise a plurality of pieces of data, and each piece of data can be in a selected state or a non-selected state. And the related personnel can select the required requirement item information in the requirement item information inquiry result display area, and click a 'determination' button to enable the Git graphical client to acquire the requirement item information. Therefore, related personnel are not required to manually input the information of the required item, the problem of low efficiency and error easiness caused by manual input is avoided, and the efficiency and accuracy of acquiring the information of the required item are improved.

In one embodiment, the program problem management system provides a program problem information query interface, and in response to receiving a second operation facing a second area on the graphical interface, invokes the second query interface to access the program problem management system to obtain program problem information, including: responding to receiving a second operation facing a second area on the graphical interface, calling a second query interface to access a program problem information query interface, and displaying program problem information query conditions and program problem information in the program problem information query interface; program problem information is received from a program problem management system.

In this embodiment, the program problem information query interface provided by the program problem management system may be used for a related person to query and display program problem information through the program problem information query condition. The program problem information query interface provided by the program problem management system may be similar to the demand item information query interface shown in fig. 4.

In an alternative embodiment, the program problem information query interface may include a fourth area and a program problem information query result display area, and the fourth area may include program problem information query conditions, and a "search" button and a "ok" button. After the program problem information query condition is determined, the related person may click a "search" button, so that the program problem information searched for by the program problem information query condition may be displayed in a program problem information query result display area, and the program problem information displayed in the program problem information query result display area may include a plurality of pieces of data, each of which may be in a selected state or a non-selected state. And the related personnel can select the needed program problem information in the program problem information inquiry result display area, and click a 'determination' button to enable the Git graphical client to acquire the program problem information. Therefore, related personnel are not required to manually input program problem information, the problem of low efficiency and error easiness caused by manual input is avoided, and the efficiency and accuracy of acquiring the program problem information are improved.

Alternatively, the program problem information query interface may be completely different from the requirement item information query interface shown in fig. 4, so long as the program problem information query conditions may be displayed through the program problem information query interface, and the queried program problem information may be displayed and the selected program problem information may be determined.

In one embodiment, the requirement item information query condition and the program problem information query condition each include at least one of: coding related personnel, version planning of target software engineering, name of target software engineering, task type, task coding and task state.

In this embodiment, the requirement item information query condition and the program problem information query condition may be identical, may be partially identical, or may be completely different.

Specifically, the codes of related personnel, the version plan of the target software project, the names of the target software project, the task types, the task codes, the task states and the like included in the requirement item information query condition and the program problem information query condition can be all obtained automatically, can be obtained partially automatically, can be input partially manually or can be input fully manually, and can be selected according to the actual needs of the related personnel, so that errors caused by manual input can be reduced to the greatest extent.

For example, since each related person clones the Git version library to have authority control, the address (url) of the cloned Git version library used by each related person has own ID, so that the code (ID) of the related person can be automatically obtained according to the cloned Git version library url, that is, the Git graphic client can intercept the ID of the related person according to the cloned Git version library url. In addition, the code branches used by the Git development are also generally related to the version plan of the Git, so the Git graphical client can also automatically select the version plan according to the code branches.

In an alternative embodiment, other requirement item information query conditions and program problem information query conditions can be selected by related personnel, or related personnel can configure default values according to own use habits. After the requirement item information query condition and/or the program problem information query condition are determined, related personnel automatically query by calling a first query interface and/or a second query interface through clicking a search button, and the returned query results are subjected to format unification to obtain submitted information, and then the submitted information is displayed and displayed, for example, as shown in fig. 3.

In an alternative embodiment, the partial demand item information query conditions and the program problem information query conditions may be manually entered or manually selected by the relevant personnel. The requirement item information meeting the condition can be searched through the requirement item information query condition, and the program problem information meeting the condition can be searched through the program problem information query condition. The query result comprises the requirement item information or the program problem information which can be displayed in a list, and related personnel can select and determine the data in the list by themselves, so that the returned requirement item information and/or the program problem information can be automatically recorded into a submission template provided by the Git graphical client to obtain the submission information, and the unification of the formats of the requirement item information and/or the program problem information is completed, thereby reducing the workload of developers. After the submitted information is obtained, the developer can directly submit the obtained submitted information to the Git server for storage.

Optionally, the requirement item information is acquired through the requirement item management system, and the program problem information is acquired through the program problem management system, so that related personnel do not need to manually input the requirement item information and/or the program problem information, the problem of low efficiency and error easiness caused by manual input is avoided, and the efficiency and accuracy for acquiring the requirement item information and/or the program problem information are improved.

In one embodiment, the commit type of the commit message includes at least one of: code modification type, configuration file modification type, program problem modification type.

In this embodiment, after the target software engineering is online, if there is a new requirement or a program problem occurs, the source code of the target software engineering needs to be modified, and then code submission is performed on the online according to the modified source code. The submission information may represent modification content when the code is submitted, and the modification may be modification of the source code according to requirements (including a unit test program related to the source code), modification of the configuration file according to requirements, and modification of the code according to a program problem.

In an alternative embodiment, after determining the submission type of the submitted information, when the source code is queried according to the submitted information, the modified content can be rapidly located, and the query efficiency of the source code is improved.

Alternatively, the code modification type and the configuration file modification type of the submitted information may be queried through the requirement item information, and the program problem modification type of the submitted information may be queried through the program problem information.

In one embodiment, the plurality of submissions is provided, each submission associated with at least one requirement item information and/or at least one program problem information.

In this embodiment, the Git graphical client requests that the submitted information need to be associated with the requirement item information and/or the program problem information, otherwise, after modifying the source code of the target software project, the modified source code cannot be submitted online. Therefore, in order to ensure that after the source code of the target software engineering is modified, the program can normally submit online, at least one piece of requirement item information and/or at least one piece of program problem information need to be associated with the submitted information, so that all pieces of submitted information are ensured to have associated requirement item information or program problem information, and the corresponding submitted information and the modification content represented by the submitted information can be queried through the serial number of the requirement item information or the serial number of the program problem information.

Optionally, the association number of the associated requirement item information and/or the program problem information can be set by the related personnel, but when the association number needs to be set with a threshold value, the associated requirement item information and/or the program problem information is not allowed to be continuously associated with the submitted information when the association number exceeds the set threshold value.

Preferably, a commit message is associated with a demand item message or a program problem message.

According to the source code query method provided by the embodiment, a demand item management system, a program problem management system and a Git graphical client are mutually independent. The Git graphical client can perform Git operation in an imaging mode, and can acquire the information of the required item and/or the program problem information by directly clicking a related button without inputting a command line, so that manual operation is reduced, the problem of low efficiency and error easiness caused by the manual operation is avoided, and the efficiency and the accuracy for acquiring the information of the required item and/or the program problem information are improved; and the acquired demand item information and/or program problem information can be automatically recorded into a preset submitted information template, and the format of the submitted information is unified, so that the query efficiency can be improved and the source code tracing corresponding to the demand item information and/or program problem information can be completed when the source code of the target software project is queried according to the submitted information later.

The embodiment of the application also provides a query device of the source code, which can be applied to the Git graphical client, wherein the Git graphical client accesses the program problem management system by calling the first query interface, the Git graphical client accesses the program problem management system by calling the second query interface, the program problem management system is used for storing the program problem information of the target software project, and the program problem management system is used for storing the program problem information of the target software project. Fig. 5 is a schematic structural diagram of a source code query device according to an embodiment of the present application, and as shown in fig. 5, a source code query device 500 includes:

An obtaining module 501, configured to invoke a first query interface to access a requirement item management system in response to receiving a request for obtaining requirement item information, obtain requirement item information, and/or invoke a second query interface to access a program problem management system in response to receiving a request for obtaining program problem information, obtain program problem information;

the format conversion module 502 is configured to perform format conversion on the requirement item information and/or the program problem information according to a preset format, so as to obtain submitted information;

and the query module 503 is configured to query source codes corresponding to the requirement item information and/or the program problem information according to the submitted information.

Optionally, the Git graphical client provides a graphical interface, and the obtaining module 501 is specifically configured to, when receiving a request for obtaining the requirement item information, invoke the first query interface to access the requirement item management system to obtain the requirement item information, and/or, when receiving a request for obtaining the program problem information, invoke the second query interface to access the program problem management system to obtain the program problem information: in response to receiving a first operation facing a first area on the graphical interface, calling a first query interface to access a demand item management system to acquire demand item information, wherein the first operation generates a request for acquiring the demand item information; and/or, in response to receiving a second operation facing a second area on the graphical interface, invoking a second query interface to access the program problem management system to obtain program problem information, the second operation generating a request for obtaining the program problem information.

Optionally, the requirement item management system provides a requirement item information query interface, and the obtaining module 501, when responding to receiving a first operation facing a first area on the graphical interface, invokes the first query interface to access the requirement item management system to obtain the requirement item information, is specifically configured to: responding to the received first operation facing the first area on the graphical interface, calling a first query interface to access a demand item information query interface, and displaying demand item information query conditions and demand item information in the demand item information query interface; demand item information is received from a demand item management system.

Optionally, the program problem management system provides a program problem information query interface, and the obtaining module 501, when responding to receiving a second operation facing a second area on the graphical interface, invokes the second query interface to access the program problem management system to obtain the program problem information, is specifically configured to: responding to receiving a second operation facing a second area on the graphical interface, calling a second query interface to access a program problem information query interface, and displaying program problem information query conditions and program problem information in the program problem information query interface; program problem information is received from a program problem management system.

Optionally, the requirement item information query condition and the program problem information query condition each include at least one of: coding related personnel, version planning of target software engineering, name of target software engineering, task type, task coding and task state.

Optionally, the submission type of the submission information includes at least one of: code modification type, configuration file modification type, program problem modification type.

Optionally, the plurality of submitted information is provided, each of the submitted information being associated with at least one requirement item information and/or at least one program problem information.

The technical scheme of the source code query device provided in this embodiment for executing the source code query method in the foregoing method embodiment is similar to the implementation principle and technical effect, and is not described herein again.

The embodiment of the application also provides electronic equipment. Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application, where the electronic device may be configured to run the aforementioned Git graphic client.

The electronic device 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an input/output interface 612, a sensor component 614, and a communication component 616. The input/output interface 612 may also be referred to as an I/O interface 612.

The processing component 602 generally controls overall operation of the electronic device 600, such as operations associated with display, data interaction, and the like. The processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.

The memory 604 is configured to store various types of data to support operations at the electronic device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, user category feature data, user feature data, and the like. The Memory 604 may be implemented by any type or combination of volatile or non-volatile Memory devices, such as Static Random-Access Memory (SRAM), electrically erasable programmable Read-Only Memory (EEPROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory EPROM), programmable Read-Only Memory (Programmable Read Only Memory PROM), read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk.

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

The multimedia component 608 includes a screen between the electronic device 600 and the user that provides an output interface. In some embodiments, the screen may include a liquid crystal display (Liquid Crystal Display, abbreviated as LCD) and a Touch panel (Touch Pad, abbreviated as TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel.

The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 600 is in an operational mode, such as a speech recognition mode. The received audio signals may be further stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.

The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 614 includes one or more sensors for providing status assessment of various aspects of the electronic device 600. For example, the sensor assembly 614 may detect an on/off state of the electronic device 600, a relative positioning of the assemblies, such as a display and keypad of the electronic device 600, and the sensor assembly 614 may also detect the presence or absence of user contact with the electronic device 600.

The communication component 616 is configured to facilitate communication between the electronic device 600 and other devices, either wired or wireless. The electronic device 600 may access a wireless network based on a communication standard, such as WiFi,4G, or 5G, or a combination thereof. In one exemplary embodiment, the communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 616 further includes a near field communication (Near Field Communication, NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on radio frequency identification (Radio Frequency Identification, abbreviated as RFID) technology, infrared data association (Infrared Data Association, abbreviated as IrDA) technology, ultra Wide Band (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the electronic device 600 may be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), digital signal processors (Digital Signal Processor, abbreviated as DSP), digital signal processing devices (Digital Signal Processor Device, abbreviated as DSPD), programmable logic devices (programmable logic device, abbreviated as PLD), field programmable gate arrays (Field programmable gate array, abbreviated as FPGA), controllers, microcontrollers, microprocessors, or other electronic elements for performing the methods described above.

In an exemplary embodiment, a non-transitory computer-readable storage medium is also provided, such as memory 604, including instructions executable by processor 620 of electronic device 600 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random access Memory (Random Access Memory, RAM for short), compact disk read-Only Memory (Compact Disc Read-Only Memory, CD-ROM for short), magnetic tape, floppy disk, optical data storage device, etc.

A non-transitory computer readable storage medium, which when executed by a processor of the electronic device 600, enables the electronic device 600 to perform the above-described source code querying method.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and the computer execution instructions are used for realizing the technical scheme of the source code query method provided in the method embodiment when being executed.

The embodiment of the application also provides a computer program product, which comprises a computer program, wherein the computer program is used for realizing the technical scheme of the source code query method provided in the method embodiment when being executed.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present application is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are alternative embodiments, and that the acts and modules referred to are not necessarily required for the present application.

It should be further noted that, although the steps in the flowchart are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.

It will be appreciated that the device embodiments described above are merely illustrative and that the device of the application may be implemented in other ways. For example, the division of the modules in the above embodiment is merely a logic function division, and there may be another division manner when actually implemented. For example, multiple units, modules, or components may be combined, or may be integrated into another system, or some features may be omitted or not performed.

In addition, unless specifically stated otherwise, each functional module in each embodiment of the present application may be integrated into one unit/module, or each unit/module may exist alone physically, or two or more units/modules may be integrated together. The integrated units/modules described above may be implemented either in hardware or in software program modules.

The integrated units/modules, if implemented in hardware, may be digital circuits, analog circuits, etc. Physical implementations of hardware structures include, but are not limited to, transistors, memristors, and the like. The processor may be any suitable hardware processor, such as CPU, GPU, FPGA, DSP and ASIC, etc., unless otherwise specified. Unless otherwise indicated, the storage elements may be any suitable magnetic or magneto-optical storage medium, such as resistive Random Access Memory RRAM (Resistive Random Access Memory), dynamic Random Access Memory DRAM (Dynamic Random Access Memory), static Random Access Memory SRAM (Static Random-Access Memory), enhanced dynamic Random Access Memory EDRAM (Enhanced Dynamic Random Access Memory), high-Bandwidth Memory HBM (High-Bandwidth Memory), hybrid Memory cube HMC (Hybrid Memory Cube), etc.

The integrated units/modules may be stored in a computer readable memory if implemented in the form of software program modules and sold or used as a stand-alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in whole or in part in the form of a software product stored in a memory, comprising several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the present application. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments. The technical features of the foregoing embodiments may be arbitrarily combined, and for brevity, all of the possible combinations of the technical features of the foregoing embodiments are not described, however, all of the combinations of the technical features should be considered as being within the scope of the disclosure.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. The query method of the source code is characterized by being applied to a Git graphical client, wherein the Git graphical client accesses a program problem management system by calling a first query interface, the Git graphical client accesses the program problem management system by calling a second query interface, the program problem management system is used for storing the program problem information of a target software project, and the program problem management system is used for storing the program problem information of the target software project;

The query method of the source code comprises the following steps:

in response to receiving a request for acquiring the requirement item information, invoking the first query interface to access the requirement item management system, acquiring the requirement item information, and/or in response to receiving a request for acquiring the program problem information, invoking the second query interface to access the program problem management system, and acquiring the program problem information;

according to a preset format, carrying out format conversion on the requirement item information and/or the program problem information to obtain submitted information;

and inquiring source codes corresponding to the requirement item information and/or the program problem information according to the submitted information.

2. A query method as claimed in claim 1, wherein said Git graphical client provides a graphical interface, said invoking said first query interface to access said demand item management system to obtain said demand item information in response to receiving a request for obtaining said demand item information, and/or said invoking said second query interface to access said program problem management system to obtain said program problem information in response to receiving a request for obtaining said program problem information, comprising:

Responding to receiving a first operation facing a first area on the graphical interface, calling the first query interface to access the requirement item management system, and acquiring the requirement item information, wherein the first operation generates a request for acquiring the requirement item information; and/or the number of the groups of groups,

and in response to receiving a second operation facing a second area on the graphical interface, calling the second query interface to access the program problem management system to acquire the program problem information, wherein the second operation generates a request for acquiring the program problem information.

3. The query method of claim 2, wherein the demand item management system provides a demand item information query interface, and the invoking the first query interface to access the demand item management system to obtain the demand item information in response to receiving a first operation directed to a first region on the graphical interface comprises:

responding to the received first operation facing the first area on the graphical interface, calling the first query interface to access the requirement item information query interface, and displaying requirement item information query conditions and requirement item information in the requirement item information query interface;

The demand item information is received from the demand item management system.

4. The query method of claim 2, wherein the program problem management system provides a program problem information query interface, and wherein the invoking the second query interface to access the program problem management system to obtain the program problem information in response to receiving a second operation directed to a second region on the graphical interface comprises:

responding to receiving a second operation facing a second area on the graphical interface, calling the second query interface to access the program problem information query interface, and displaying program problem information query conditions and program problem information in the program problem information query interface;

program problem information is received from the program problem management system.

5. The query method of claim 3 or 4, wherein the requirement information query condition and the program problem information query condition each include at least one of: and the related personnel code, the version plan of the target software project, the name of the target software project, the task type, the task code and the task state.

6. The query method of any of claims 1 to 4, wherein the commit type of commit information includes at least one of: code modification type, configuration file modification type, program problem modification type.

7. The query method of any one of claims 1 to 4, wherein the submitted information is a plurality of, each associated with at least one requirement item information and/or at least one program problem information.

8. The query device of the source code is characterized by being applied to a Git graphical client, wherein the Git graphical client accesses a program problem management system by calling a first query interface, the Git graphical client accesses the program problem management system by calling a second query interface, the program problem management system is used for storing the program problem information of a target software project, and the program problem management system is used for storing the program problem information of the target software project;

the query device of the source code comprises:

the acquisition module is used for calling the first query interface to access the requirement item management system in response to receiving a request for acquiring the requirement item information and/or calling the second query interface to access the program problem management system in response to receiving the request for acquiring the program problem information and acquiring the program problem information;

The format conversion module is used for carrying out format conversion on the requirement item information and/or the program problem information according to a preset format to obtain submitted information;

and the query module is used for querying the source codes corresponding to the requirement item information and/or the program problem information according to the submitted information.

9. The query device of claim 8, wherein the Git graphical client provides a graphical interface, and wherein the acquisition module is configured to invoke the first query interface to access the demand item management system to acquire the demand item information in response to receiving a request to acquire the demand item information, and/or to invoke the second query interface to access the program issue management system to acquire the program issue information in response to receiving a request to acquire the program issue information by:

10. An electronic device, comprising: a processor, and a memory coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1 to 7.

11. A computer readable storage medium having stored therein computer executable instructions which when executed are adapted to implement the method of any one of claims 1 to 7.

12. A computer program product comprising a computer program for implementing the method of any one of claims 1 to 7 when executed.