CN117008922A - Client hook configuration method, device, equipment and medium - Google Patents

Abstract

This application discloses a client hook configuration method, device, equipment and medium, which relates to the field of computer technology, including: obtaining the target code project corresponding to the client from the distributed version control system warehouse; obtaining the corresponding target code project from the target code project Hook configuration file; parse the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions, create a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after the analysis, and use the hook file to install Directives and target hook files configure and install the corresponding target client hooks locally. Store the hook configuration file in the code project in the remote distributed version control system warehouse. Each client that develops and processes the code project can obtain the configuration parameter information of the client hook when acquiring the code project without having to download it locally. You can customize settings on the client and install client hooks on the local client with one click.

Description

A client hook configuration method, device, equipment and medium

Technical field

The present invention relates to the field of computer technology, and in particular to a client hook configuration method, device, equipment and medium.

Background technique

Currently in the field of software development technology, the Git distributed version control system can track file changes and record the history of these changes. Using Git, multiple developers can work together to create branches, commit changes, merge modifications, and roll back to previous versions. The process for users to use Git hooks is: enter the root directory of their respective Git repositories. Find the .git/hooks directory. This directory contains sample files for various hooks. Select the appropriate hook as needed, rename the sample files and remove the suffix. For example, select the pre-commit (pre-run hook type) sample file and rename it to pre-commit. Edit hook files to add custom logic and scripts. Shell scripts or other appropriate programming languages can be used. Save the hook file and make sure it has executable permissions. The hook will now automatically execute the custom script when the corresponding Git action is triggered. Git hooks are only valid for local repositories, and each developer needs to set up hooks individually. If there are multiple developers working together, they need to configure corresponding hooks in their respective local repositories.

To sum up, how to prevent each user from editing the hook file on his or her own client and realize simple installation/uninstallation of hooks on the client is a technical problem to be solved in this field.

Contents of the invention

In view of this, the purpose of the present invention is to provide a client hook configuration method, device, equipment and medium, which can prevent each user from editing hook files on their own client and realize simple installation/uninstallation of hooks on the client. The specific plan is as follows:

In the first aspect, this application discloses a client hook configuration method, which is applied to the client and includes:

Obtain the target code project corresponding to the client from the distributed version control system warehouse;

Obtain the corresponding hook configuration file from the target code project; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured;

The hook configuration file is parsed through a hook configuration tool and based on configuration file parsing instructions, a target hook file corresponding to the target configuration parameter information is created based on the target configuration parameter information obtained after analysis, and the hook file installation instructions are used and the target hook file configures and installs the corresponding target client hook locally.

Optionally, obtaining the corresponding hook configuration file from the target code project includes:

Determine the target hook configuration file from all the hook configuration files according to the hook configuration file placement order in the preset file placement directory of the target code project;

Or, determine the target hook configuration file from all said hook configuration files based on the path of the specified target hook configuration file included in the hook configuration file acquisition instruction;

Correspondingly, the hook configuration file is parsed through the hook configuration tool and based on the configuration file parsing instructions, and a target hook file corresponding to the target configuration parameter information is created based on the target configuration parameter information obtained after the analysis, including :

Detect whether the dependencies integrated with the hook configuration tool associated with the target code project are installed, and if the installation is completed, generate a configuration file parsing instruction;

The target hook configuration file is parsed through the hook configuration tool and based on the configuration file parsing instructions, and the corresponding target hook file is created based on the pre-commit hook type parameter information or pre-run hook type parameter information obtained after the analysis.

Optionally, the target hook configuration file is parsed through the hook configuration tool and based on the configuration file parsing instructions, and the corresponding target hook file is created based on the pre-submit hook type parameter information or pre-run hook type parameter information obtained after the analysis. ,include:

Determine the file type of the target hook configuration file, and select a file parsing tool corresponding to the file type from the hook configuration tool to perform file parsing on the target hook configuration file;

Create the corresponding target hook file based on the parsed pre-commit hook type parameter information or pre-run hook type parameter information.

Optionally, after creating the corresponding target hook file based on the parsed pre-submit hook type parameter information or pre-run hook type parameter information, it also includes:

Use the hook configuration tool to determine the relationship between the version number of the current distributed version control system and the preset version number, and obtain the corresponding version number judgment result;

Based on the version number judgment result, the writing method of the target hook file is selected to be writing into a folder or into a hook directory, and based on the version number judgment result, the target hook file is written into the corresponding target folder or Target hook directory.

Optionally, before obtaining the corresponding hook configuration file from the target code project, the following steps are also included:

Name all hook configuration files according to the preset naming rules, and store all renamed hook configuration files in the preset file placement directory.

Optionally, before obtaining the corresponding hook configuration file from the target code project, the following steps are also included:

The path information stored in the hook configuration file corresponding to the target client hook is used as the specified target configuration file path, and the specified target configuration file path is configured into the hook configuration file acquisition instruction.

Optionally, the hook configuration tool is installed in the client, so that the client parses, configures and installs the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions and the hook file installation instructions.

Optionally, after the hook file installation instructions and the target hook file are configured locally and the corresponding target client hook is installed, the following is also included:

When it is detected that the client executes the current operation of the distributed version control system, the client is triggered to store the corresponding target client hook, execute the script program corresponding to the target client hook, and obtain the execution operation result;

If the operation is successful, continue to perform the next operation of the distributed version control system;

If the operation fails, the current operation of the distributed version control system is blocked.

Optionally, the client hook configuration method also includes:

If a hook file uninstall instruction is detected, the hook file information of the client hook to be uninstalled is obtained from the hook file uninstall instruction, so as to use the hook file information to uninstall the corresponding target client hook from the client.

In the second aspect, this application discloses a client hook configuration device, which is applied to the client and includes:

The project acquisition module is used to acquire the target code project corresponding to the client from the distributed version control system warehouse;

A file acquisition module is used to obtain the corresponding hook configuration file from the target code project; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured;

A hook parsing configuration module is used to parse the hook configuration file through a hook configuration tool and based on configuration file parsing instructions, and create a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after parsing. , and use the hook file installation instructions and the target hook file to locally configure and install the corresponding target client hook.

In a third aspect, this application discloses an electronic device, including:

Memory, used to hold computer programs;

A processor, configured to execute the computer program to implement the steps of the aforementioned disclosed client hook configuration method.

In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein when the computer program is executed by a processor, the steps of the aforementioned disclosed client hook configuration method are implemented.

It can be seen that this application discloses a client hook configuration method, which is applied to the client, including: obtaining the target code project corresponding to the client from the distributed version control system warehouse; obtaining the target code project from the target code project Obtain the corresponding hook configuration file; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured; the hook configuration file is parsed through the hook configuration tool and based on the configuration file parsing instructions. Based on the parsing The target configuration parameter information obtained later creates a target hook file corresponding to the target configuration parameter information, and uses the hook file installation instruction and the target hook file to configure and install the corresponding target client hook locally. It can be seen that by obtaining the hook configuration file in the target code project, then creating the corresponding target hook file on the local client based on the target configuration parameter information in the parsed hook configuration file, and then using the created target hook file and hook file installation instructions directly Configure and install the target client hook, store the target configuration parameter information corresponding to the client hook in the hook configuration file, and then store the hook configuration file in the code project in the remote distributed version control system warehouse, so that Each client that needs to develop and process the code project can obtain the configuration parameter information of the client hook when acquiring the code project, without having to customize the settings on the local side, so that the client can be installed with one click on the local client. hook.

Description of the drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only These are embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on the provided drawings without exerting creative efforts.

Figure 1 is a flow chart of a client hook configuration method disclosed in this application;

Figure 2 is a diagram of the analysis of a configuration file disclosed in this application and the writing of the corresponding hook file;

Figure 3 is a flow chart of a specific client hook configuration method disclosed in this application;

Figure 4 is a flow chart of a method for setting git hooks in a configuration file disclosed in this application;

Figure 5 is a schematic structural diagram of a client hook configuration device disclosed in this application;

Figure 6 is a structural diagram of an electronic device disclosed in this application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present invention.

Currently in the field of software development technology, the Git distributed version control system can track file changes and record the history of these changes. Using Git, multiple developers can work together to create branches, commit changes, merge modifications, and roll back to previous versions. The process for users to use Git hooks is: enter the root directory of their respective Git repositories. Find the .git/hooks directory. This directory contains sample files for various hooks. Select the appropriate hook as needed, rename the sample files and remove the suffix. For example, select the pre-commit sample file and rename it to pre-commit. Edit hook files to add custom logic and scripts. Shell scripts or other appropriate programming languages can be used. Save the hook file and make sure it has executable permissions. The hook will now automatically execute the custom script when the corresponding Git action is triggered. Git hooks are only valid for local repositories, and each developer needs to set up hooks individually. If there are multiple developers working together, they need to configure corresponding hooks in their respective local repositories.

To this end, this application provides a client hook configuration solution, which can prevent each user from editing the hook file on their own client and realize simple installation/uninstallation of hooks on the client.

Referring to Figure 1, an embodiment of the present invention discloses a client hook configuration method, which is applied to the client and includes:

Step S11: Obtain the target code project corresponding to the client from the distributed version control system warehouse.

In this embodiment, the target code project that meets the client's needs is copied from the remote warehouse of the remote distributed version control system Git. Specifically, after the user logs in from the local client, based on his own project needs, he accesses through the access command. Git's remote warehouse, and then read and copy the corresponding target code project from the remote read-write warehouse or remote read warehouse based on the target code project copy copy command, and then pull the copied target code project to the local warehouse of the local system, using For object code project development work, etc.

Step S12: Obtain the corresponding hook configuration file from the target code project; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured.

In this embodiment, the hook configuration file is queried from the obtained target code project. The hook configuration file in the target code project contains target configuration parameter information corresponding to several client hooks to be configured. In other words, the hook The configuration file can contain target configuration parameter information corresponding to all existing Git hooks.

In this embodiment, before obtaining the hook configuration files, all hook configuration files are named according to the preset naming rules, and all the renamed hook configuration files are stored in the preset file placement directory; or, with The path information stored in the hook configuration file corresponding to the target client hook is used as the specified target configuration file path, and the specified target configuration file path is configured into the hook configuration file acquisition instruction. Specifically, in a specific implementation manner, the hook configuration file sets a unified naming rule, such as: gitHookConfig.xml, gitHookConfig.json, gitHookConfig.yaml, etc. In this way, a file placement directory needs to be fixed, such as: Project root directory. In another specific implementation, the path information of the target hook configuration file can also be specified in the parameter of the configuration file acquisition instruction, for example: githook install-file=/config/gitHook.json.

In this embodiment, obtaining the corresponding hook configuration file from the target code project includes: determining the target from all the hook configuration files according to the placement order of the hook configuration files in the preset file placement directory of the target code project. Hook configuration file; or, determine the target hook configuration file from all the hook configuration files based on the path of the specified target hook configuration file contained in the hook configuration file acquisition instruction; It can be understood that, in a specific implementation, execute When the configuration file obtains the instruction, the file configuration program will automatically search for the gitHookConfig.json file in the project root directory to obtain the target hook configuration file. In another specific implementation, when receiving the configuration file acquisition instruction, it will directly The path information of the specified target hook configuration file in the configuration file acquisition instruction finds the target hook configuration file where the path information is stored in the target project. Supports automatic identification of hook configuration files according to rules and command-specified target hook configuration files.

In this embodiment, the hook configuration file in the Git project is subject to the version management of the Git repository and can be developed through team collaboration. The hook configuration file can be used in any format, such as JSON (JavaScript Object Notation), XML (Extensible Markup) Language, extensible markup language), YAML (Yet Another MarkupLanguage, markup language), etc. The configuration file stores the Git Hook information that needs to be configured. Since a configuration file is a file used to store the settings and parameters of a program, system or application. They usually use a specific format, such as XML format, JSON format, or YAML format, to organize and describe various configuration options. The configuration file contains various settings for the application, such as database connection information, log levels, API keys for external services, etc. By modifying the values in the configuration file, you can change the behavior and functionality of the program. Configuration files provide a flexible and maintainable way to customize and configure applications. Rather than having to hardcode these settings in the code, this makes the program easier to deploy, maintain, and extend.

Step S13: Parse the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions, create a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after analysis, and use the hook The file installation instructions and the target hook file configure and install the corresponding target client hook locally.

In this embodiment, it is detected whether the dependencies integrated with the hook configuration tool associated with the target code project are installed. If the installation is completed, a configuration file parsing instruction is generated; the hook configuration tool is used and based on the configuration file parsing instruction. The target hook configuration file is parsed, and the corresponding target hook file is created based on the parsed pre-submit hook type parameter information or pre-run hook type parameter information. It is understandable that to detect whether the hook configuration tool has been installed, specifically to detect whether the Git Hook configuration tool installed in the local machine has been successfully installed. If it is successfully installed, a configuration file parsing instruction will be generated, through the hook configuration tool and based on the configuration file. The parsing instruction parses the target hook configuration file, and creates a corresponding target hook file based on the pre-commit parameter information or pre-push parameter information obtained after parsing. Since the specific content in the target hook configuration file is generally in the Key-Value format, Key is the Hook type of Git, such as pre-commit, pre-push, etc., and Value is the command that the corresponding hook needs to execute.

In this embodiment, parsing the target configuration file specifically includes: determining the file type of the target hook configuration file, and selecting a file parsing tool corresponding to the file type from the hook configuration tool to perform analysis on the target hook configuration file. File parsing; create the corresponding target hook file based on the parsed pre-submit hook type parameter information or pre-run hook type parameter information. It is understandable that after determining the target hook configuration file, use the corresponding file parsing tool according to the file type and parse the file content based on the configuration file parsing instructions. File parsing tools can be used for file parsing in corresponding languages. For example, general parsing tools corresponding to JSON and XML file types can be used to parse the target hook configuration file corresponding to the corresponding file type, based on the parsed hook type parameter information. Create the corresponding target hook file. Referring to Figure 2, taking the JSON file type as an example, parse the target hook configuration file of this type. When the hook configuration file contains the pre-commit parameter information and pre-push parameter information corresponding to the three client hooks to be configured, respectively and commit-msg parameter information, obtain the target hook configuration file according to the actual hook requirements of the client. When the target hook configuration file is pre-commit, create and write do somethingprecommit to the Hook folder. When the target hook configuration file is pre-commit, When pushing, create and write do somethingpre-push to the Hook folder. When the target hook configuration file is commit-msg, create and access do somethingcommit-msg to the Hook folder. It can be seen that Git Hook is set up by using the configuration file. Supports different types of configuration file parsing settings. And one configuration file supports multiple Git Hook configurations.

In this embodiment, after creating the corresponding target hook file based on the parsed pre-commit hook type parameter information or pre-run hook type parameter information, it also includes: determining the version number of the current distributed version control system through the hook configuration tool. relationship with the preset version number, and obtain the corresponding version number judgment result; based on the version number judgment result, select the writing method of the target hook file as writing to the folder or writing to the hook directory, and based on the The version number judgment result writes the target hook file to the corresponding target folder or target hook directory. It is understandable that after the target hook file is created, the corresponding Hook and command content will be written to the git hook folder. In lower versions of Git, it needs to be written to the .git/hooks folder, for example: the content of the pre-commit file is dosomething check. The Hooks folder setting function is supported after Git2.9 version. You can set the Git hooks folder by configuring core.hooksPath. The hook configuration tool will automatically determine the version and configuration of Git, and you can set the Hooks file to the correct Hooks. in the directory. Compatible with different versions of Git Hook setup directories.

In this embodiment, the hook file installation instruction and the generated target hook file are used to locally configure and install the corresponding target client hook, which facilitates one-click installation of all Git Hooks.

It can be seen that this application discloses a client hook configuration method, which is applied to the client, including: obtaining the target code project corresponding to the client from the distributed version control system warehouse; obtaining the target code project from the target code project Obtain the corresponding hook configuration file; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured; the hook configuration file is parsed through the hook configuration tool and based on the configuration file parsing instructions. Based on the parsing The target configuration parameter information obtained later creates a target hook file corresponding to the target configuration parameter information, and uses the hook file installation instruction and the target hook file to configure and install the corresponding target client hook locally. It can be seen that by obtaining the hook configuration file in the target code project, then creating the corresponding target hook file on the local client based on the target configuration parameter information in the parsed hook configuration file, and then using the created target hook file and hook file installation instructions directly Configure and install the target client hook, store the target configuration parameter information corresponding to the client hook in the hook configuration file, and then store the hook configuration file in the code project in the remote distributed version control system warehouse, so that Each client that needs to develop and process the code project can obtain the configuration parameter information of the client hook when acquiring the code project, without having to customize the settings on the local side, so that the client can be installed with one click on the local client. hook.

Referring to FIG. 3 , an embodiment of the present invention discloses a specific client hook configuration method. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. specific:

Step S21: Obtain the target code project corresponding to the client from the distributed version control system warehouse.

Step S22: Obtain the corresponding hook configuration file from the target code project; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured.

Step S23: The hook configuration tool is installed in the client, so that the client parses, configures and installs the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions and the hook file installation instructions.

In this embodiment, the Git Hook configuration tool is a tool program device. The tool program device can be installed in the local client, so that on the client side, you can parse the configuration file through the tool program device and the configuration file parsing instructions, and convert the configuration file into The corresponding Git Hook is parsed into the corresponding Hook file.

Step S24: Parse the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions, create a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after the analysis, and The corresponding target client hook is locally configured and installed using the hook file installation instruction and the target hook file.

For more detailed processing procedures in steps S21, S22, and S24, please refer to the previously disclosed embodiments and will not be described again here.

Step S25: When it is detected that the client executes the current operation of the distributed version control system, trigger the client to store the corresponding target client hook, execute the script program corresponding to the target client hook, and Obtain the execution operation result; if the operation is successful, continue to execute the next operation of the distributed version control system; if the operation fails, block the current operation of the distributed version control system.

In this embodiment, when it is detected that a client user performs a corresponding Git operation, such as git commit, the corresponding hook will be automatically triggered and the relevant script program will be executed. When the script program is successfully executed, the corresponding Git operation will continue to be executed. When the script program fails to execute, the Git operation will be prevented from continuing. Among them, the specific execution operations using hooks may include:

1. Verify submission specifications:

Use the pre-commit hook to run a script to check the submission information format, code specifications, etc. before submitting the code.

2. Run the test:

Use the pre-commit hook to run the test suite before submission to ensure that the submitted code passes the unit test.

3. Prevent the leakage of sensitive information:

Use the pre-commit hook to check whether the code contains sensitive information (such as API keys, passwords), etc. before submission to avoid accidentally submitting it to the repository.

4. Automatically format code:

Use pre-commit hooks to run code formatting tools (such as Prettier, Black, etc.) before submission to ensure code consistency and readability.

5. Control access rights:

Use server-side hooks (such as pre-receive) to verify permissions before pushing code to the remote warehouse to restrict access to specific users or branches.

Step S26: If a hook file uninstall instruction is detected, obtain the hook file information of the client hook to be uninstalled from the hook file uninstall instruction, so as to use the hook file information to uninstall the corresponding target client hook from the client.

In this embodiment, the user can send the "Uninstall Hook" instruction through the program code according to his own needs, so as to uninstall the corresponding Hook configuration that has been installed in the client based on the "Uninstall Hook" instruction, which is convenient for the user and convenient. key to uninstall all Git Hooks.

Referring to Figure 4, to set up Git hooks based on the hook configuration file, first install the hook configuration tool. The hook configuration tool does not limit the installation method. The hook configuration tool can be placed in the code project or as a dependency. Unify the installation of project dependencies, such as maven dependencies for java, npm dependencies for javascript, etc. At the same time, the hook configuration tool can also be installed in the global environment of the local system and called as a command line program or script. After the hook configuration tool is successfully installed, you can call the program's installation Hook and uninstall Hook commands.

When using the hook configuration tool, the code project must use Git. There is no restriction on the specific version of Git. Git is used for version management. There is a .git folder after initializing the project.

Secondly, parse and install the hook, specifically:

The hook configuration tool provides a command to install Hook, which will set the contents in the configuration file to the githook directory to generate the corresponding Hook file.

Parse the configuration file:

The hook configuration tool can automatically parse the corresponding configuration file or specify the configuration file using the parameters of the installation command. Automatically parsing configuration files requires setting a unified naming rule for configuration files, such as: gitHookConfig.xml, gitHookConfig.json, gitHookConfig.yaml, etc. It is necessary to fix a file placement directory, such as the project root directory. When executing the Hook installation command in this way, the hook configuration tool will automatically look for the gitHookConfig.json file in the project root directory. You can also specify the path to the target configuration file in the parameters of the installation command, for example: githook install–file=/config/gitHook.json.

After determining the target configuration file, perform file content analysis based on the file type. Here you can use the file parsing tool of the corresponding language to parse the file, such as: general parsing tool for JSON and XML files.

The specific content of the target configuration file is generally in Key-value format, and the Key is the hook type of Git, such as pre-commit, pre-push, etc. Value is the command that the corresponding Hook needs to execute.

After the hook configuration tool obtains the contents of the configuration file, it will write the corresponding Hook and command contents to the Githook folder. In lower versions of Git, it needs to be written to the .git/hooks folder. For example, the content of the pre-commit file is do something check. The Hooks folder setting function is supported after Git2.9 version. You can set the Git hooks folder by configuring core.hooksPath. The hook configuration tool will automatically determine the version and configuration of Git, and you can set the Hooks file to the correct Hooks. in the directory.

When the user performs a Git operation, for example, when performing a Git commit operation, the pre-commit file script content set by this program will be automatically triggered through the Git Hook mechanism. When the script execution is successful, continue to execute the commit operation. When the script execution fails, prevent the execution of the commit operation.

Uninstall Hook:

The hook configuration tool provides commands to uninstall Hooks, which can uninstall all Hook settings with one click, making it easier for users to control the use of Git hooks. For example: gitHook uninstall will delete the Git hook file in the corresponding hook folder.

It can be seen that in the existing technology, Git hooks are only effective for local warehouses, and each developer needs to set up hooks individually. If there are multiple developers working together, they need to configure corresponding hooks in their respective local repositories. In this application, there is no need to create, modify, or delete Git Hooks in the hidden directory .git, making editing more flexible. And there is no need to operate the corresponding files and process the corresponding permissions when compiling each type of Hook, and the process is simpler. Configuration files can be used to manage Git warehouse versions, share Git Hook settings among the team, and quickly enable and disable all Git Hooks with one click. This way, by using Git hooks, custom scripts can be executed before and after Git operations occur to automate, validate, and enhance development workflows.

Referring to Figure 5, the present invention also discloses a client hook configuration device, which is applied to the client and includes:

The project acquisition module 11 is used to acquire the target code project corresponding to the client from the distributed version control system warehouse;

The file acquisition module 12 is used to obtain the corresponding hook configuration file from the target code project; wherein the hook configuration file contains target configuration parameter information corresponding to several client hooks to be configured;

The hook parsing configuration module 13 is used to parse the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions, and create a target hook corresponding to the target configuration parameter information based on the target configuration parameter information obtained after parsing. file, and use the hook file installation instructions and the target hook file to locally configure and install the corresponding target client hook.

It can be seen that this application discloses obtaining the target code project corresponding to the client from the distributed version control system warehouse; obtaining the corresponding hook configuration file from the target code project; wherein the hook configuration file includes Target configuration parameter information corresponding to several client hooks to be configured; parse the hook configuration file through the hook configuration tool and based on the configuration file parsing instructions, and create the target configuration based on the target configuration parameter information obtained after parsing The target hook file corresponding to the parameter information, and the corresponding target client hook is locally configured and installed using the hook file installation instruction and the target hook file. It can be seen that by obtaining the hook configuration file in the target code project, then creating the corresponding target hook file on the local client based on the target configuration parameter information in the parsed hook configuration file, and then using the created target hook file and hook file installation instructions directly Configure and install the target client hook, store the target configuration parameter information corresponding to the client hook in the hook configuration file, and then store the hook configuration file in the code project in the remote distributed version control system warehouse, so that Each client that needs to develop and process the code project can obtain the configuration parameter information of the client hook when acquiring the code project, without having to customize the settings on the local side, so that the client can be installed with one click on the local client. hook.

Furthermore, the embodiment of the present application also discloses an electronic device. Figure 6 is a structural diagram of the electronic device 20 according to an exemplary embodiment. The content in the figure cannot be considered as any limitation on the scope of use of the present application.

FIG. 6 is a schematic structural diagram of an electronic device 20 provided by an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input-output interface 25 and a communication bus 26. The memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement relevant steps in the client hook configuration method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be applicable Any communication protocol of the technical solution of this application is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the external world, and its specific interface type can be selected according to specific application needs. Here Not specifically limited.

The processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can adopt at least one hardware form among DSP (Digital Signal Processing, digital signal processing), FPGA (Field-Programmable Gate Array, field programmable gate array), and PLA (Programmable Logic Array, programmable logic array). accomplish. The processor 21 may also include a main processor and a co-processor. The main processor is a processor used to process data in the wake-up state, also called CPU (Central Processing Unit, central processing unit); the co-processor is A low-power processor used to process data in standby mode. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit, image processor), and the GPU is responsible for rendering and drawing content to be displayed on the display screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence, artificial intelligence) processor, which is used to process computing operations related to machine learning.

In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be short-term storage or permanent storage. .

Among them, the operating system 221 is used to manage and control each hardware device and the computer program 222 on the electronic device 20 to realize the calculation and processing of the massive data 223 in the memory 22 by the processor 21. It can be Windows Server, Netware, Unix, Linux etc. In addition to computer programs that can be used to complete the client hook configuration method executed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs that can be used to complete other specific tasks. In addition to the data received by the electronic device and transmitted from an external device, the data 223 may also include data collected by its own input and output interface 25, etc.

Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein when the computer program is executed by a processor, the aforementioned disclosed client hook configuration method is implemented. Regarding the specific steps of this method, reference may be made to the corresponding content disclosed in the foregoing embodiments, which will not be described again here.

Each embodiment in this specification is described in a progressive manner. Each embodiment focuses on its differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple. For relevant details, please refer to the description in the method section.

Those skilled in the art may further realize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. In order to clearly illustrate the possible functions of hardware and software, Interchangeability, in the above description, the composition and steps of each example have been generally described according to functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application. The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly in hardware, in software modules executed by a processor, or in a combination of both. Software modules may be located in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or anywhere in the field of technology. any other known form of storage media.

Finally, it should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or any such actual relationship or sequence between operations. Furthermore, the terms "comprises," "comprises," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or apparatus that includes the stated element.

The client hook configuration method, device, equipment and media provided by the present invention have been introduced in detail above. This article uses specific examples to illustrate the principles and implementation modes of the present invention. The description of the above embodiments is only for It helps to understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the field, there will be changes in the specific implementation and application scope according to the idea of the present invention. In summary, the content of this specification It should not be construed as a limitation of the invention.

Claims (12)

1. The client hook configuration method is characterized by being applied to a client and comprising the following steps of:

acquiring target code items corresponding to the client from a distributed version control system warehouse;

acquiring a corresponding hook configuration file from the target code item; the hook configuration file comprises target configuration parameter information corresponding to a plurality of client hooks to be configured respectively;

analyzing the hook configuration file through a hook configuration tool based on a configuration file analysis instruction, creating a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after analysis, and locally configuring and installing corresponding target client hooks by using a hook file installation instruction and the target hook file.

2. The client hook configuration method according to claim 1, wherein the obtaining a corresponding hook configuration file from the object code item includes:

determining a target hook configuration file from all the hook configuration files according to the hook configuration file placement sequence in the preset file placement catalog of the target code item;

or determining a target hook configuration file from all the hook configuration files based on the path of the specified target hook configuration file contained in the hook configuration file acquisition instruction;

correspondingly, the parsing, by the hook configuration tool and based on a configuration file parsing instruction, the hook configuration file creating a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after parsing includes:

detecting whether the installation of the dependency item which is associated with the target code item and integrates the hook configuration tool is completed, and if the installation is completed, generating a configuration file analysis instruction;

analyzing the target hook configuration file through a hook configuration tool and based on a configuration file analysis instruction, and creating a corresponding target hook file based on pre-submitted hook type parameter information or pre-running hook type parameter information obtained after analysis.

3. The method for configuring a hook of a client according to claim 2, wherein the parsing, by a hook configuration tool and based on a configuration file parsing instruction, the target hook configuration file creates a corresponding target hook file based on pre-submitted hook type parameter information or pre-run hook type parameter information obtained after parsing, including:

determining the file type of the target hook configuration file, and selecting a file analysis tool corresponding to the file type from the hook configuration tools to analyze the file of the target hook configuration file;

and creating a corresponding target hook file based on the pre-submitted hook type parameter information or the pre-running hook type parameter information obtained after analysis.

4. The method for configuring a client hook according to claim 3, wherein after creating the corresponding target hook file based on the pre-submitted hook type parameter information or the pre-run hook type parameter information obtained after parsing, the method further comprises:

judging the relation between the version number of the current distributed version control system and a preset version number through the hook configuration tool, and acquiring a corresponding version number judgment result;

And selecting the writing mode of the target hook file to be a writing folder or a writing hook catalog based on the version number judgment result, and writing the target hook file into the corresponding target folder or target hook catalog based on the version number judgment result.

5. The client hook configuration method according to claim 2, further comprising, before the obtaining the corresponding hook configuration file from the object code item:

and naming the files of all the hook configuration files according to a preset naming rule, and storing all the renamed hook configuration files into a preset file placement catalog.

6. The client hook configuration method according to claim 2, further comprising, before the obtaining the corresponding hook configuration file from the object code item:

and taking the path information stored in the hook configuration file corresponding to the hook of the target client as a designated target configuration file path, and configuring the designated target configuration file path into a hook configuration file acquisition instruction.

7. The client hook configuration method of claim 1, wherein the hook configuration tool is installed in the client such that the client parses and configures and installs the hook configuration file through the hook configuration tool and based on configuration file parsing instructions and hook file installation instructions.

8. The client hook configuration method according to any one of claims 1 to 7, wherein after the locally configuring and installing the corresponding target client hook using the hook file installation instruction and the target hook file, further comprising:

when the current operation of the client executing the distributed version control system is detected, triggering the client to store the corresponding target client hook, executing a script program corresponding to the target client hook, and acquiring an execution operation result;

if the operation is successful, continuing to execute the next operation of the distributed version control system;

and if the operation fails, preventing the current operation of the distributed version control system.

9. The client hook configuration method of claim 1, further comprising:

if the hook file uninstalling instruction is detected, hook file information of a client hook to be uninstalled is obtained from the hook file uninstalling instruction, so that the corresponding target client hook is uninstalled from the client by utilizing the hook file information.

10. A client hook configuration apparatus, applied to a client, comprising:

The project acquisition module is used for acquiring target code projects corresponding to the client from a distributed version control system warehouse;

the file acquisition module is used for acquiring a corresponding hook configuration file from the target code item; the hook configuration file comprises target configuration parameter information corresponding to a plurality of client hooks to be configured respectively;

the hook analysis configuration module is used for analyzing the hook configuration file through a hook configuration tool based on a configuration file analysis instruction, creating a target hook file corresponding to the target configuration parameter information based on the target configuration parameter information obtained after analysis, and locally configuring and installing corresponding target client hooks by utilizing a hook file installation instruction and the target hook file.

11. An electronic device, comprising:

a memory for storing a computer program;

a processor for executing the computer program to implement the steps of the client hook configuration method of any one of claims 1 to 9.

12. A computer-readable storage medium storing a computer program; wherein the computer program when executed by a processor implements the steps of the client hook configuration method of any of claims 1 to 9.