Git-based article management system implementation method and system

Abstract

The invention provides a Git-based article management system implementation method and system, and the method comprises the steps: obtaining an article management system creation instruction of a user, and generating a user exclusive Git warehouse according to the article management system creation instruction; an article management instruction of the user is obtained, article content management is carried out on the user exclusive Git reference according to the article management instruction, and the article content is stored in a user exclusive Git warehouse in the form of a folder and a file; the method comprises the following steps: acquiring an article publishing instruction of a user, initiating a synchronization request to a user exclusive Git warehouse according to the article publishing instruction to obtain synchronization request content, and performing content auditing and version control on the synchronization request content through Git branch management and a merging request to complete article publishing of the synchronization request content. According to the method, the article content can be automatically created and managed through Git, and auditing, version control, backup and migration of the article content are realized.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a Git-based article management system implementation method and system. Background Art

[0002] Content Management System (CMS) is a software system located between the WEB front-end and back-end office systems or processes. The shortcomings of traditional content management systems are as follows:

[0003] 1. Complexity of building from scratch: The construction of traditional CMS often needs to start from scratch, involving database design, content storage structure, etc. It is necessary to design a flexible content model to adapt to different types and structures of content, organize and classify content, and manage metadata. Therefore, building a CMS is relatively complex.

[0004] 2. Content review and version control: Traditional CMS content review and version control need to be developed independently, which not only increases the development workload and extends the development cycle, but also requires consideration of user permissions, review status management, etc. The recording of review and version information also requires additional development.

[0005] 3. Complex backup and migration processes: The traditional CMS backup process is complex, and often requires the backend management interface to operate the database and file backup; the migration function is even more complicated, requiring export before import. For complex migrations, you may also need to use special plug-ins or tools to help transfer data. Summary of the invention

[0006] In order to solve the above problems in the prior art, the present invention provides a Git-based article management system implementation method and system, which can automatically create and manage article content through Git, and realize article content review, version control, backup and migration.

[0007] In order to achieve the above object, the technical solution adopted by the present invention is:

[0008] In a first aspect, the present invention provides a method for implementing an article management system based on Git, comprising the steps of:

[0009] S1. Obtain the user's article management system creation instruction, and generate a user-specific Git repository according to the article management system creation instruction;

[0010] S2. Obtain the user's article management instruction, and manage the article content of the user's exclusive Git reference according to the article management instruction, wherein the article content is stored in the user's exclusive Git repository in the form of folders and files;

[0011] S3. Obtain the user's article publishing instruction, initiate a synchronization request to the user's exclusive Git repository according to the article publishing instruction, obtain the synchronization request content, perform content review and version control on the synchronization request content through Git branch management and merge requests, and complete the article publishing of the synchronization request content.

[0012] The beneficial effects of the present invention are as follows: the present invention utilizes the natural advantages of the Git version control system to automatically form a file and directory structure without the need to pre-design a complex database structure, thereby being able to automatically create and manage article content through Git. At the same time, the branch management and merge request functions of Git are utilized to implement the review and version control of article content, without the need to separately develop content review and version control.

[0013] Optionally, the method further comprises the steps of:

[0014] S4. Obtain the user's article backup instruction, copy the user's exclusive Git repository according to the article backup instruction, and generate a user backup Git reference.

[0015] Optionally, the method further comprises the steps of:

[0016] S5. Obtain the user's article migration instructions, and push the user's exclusive Git repository to other platforms that need to be migrated according to the article migration instructions.

[0017] According to the above description, the Git repository contains all the necessary history and version information, so backup only requires copying the repository, and migration only requires pushing the repository to a new server or platform, which greatly simplifies the backup and migration processes.

[0018] Optionally, step S2 includes the following steps:

[0019] S21, obtaining the user's article classification management instruction, and managing folders under the user's exclusive Git repository according to the article classification management instruction;

[0020] S22. Obtain the user's article content management instructions, and manage files in the folder corresponding to the article category selected by the user in the user-specific Git repository according to the article content management instructions.

[0021] Optionally, the step S2 further includes the steps of:

[0022] S23, generating commit content for each management of the article content, and recording it in the commit record table of the user-specific Git repository;

[0023] The content review of the synchronization request content in step S3 includes providing the commit content for review by a reviewer.

[0024] Optionally, the branch management in step S3 is:

[0025] A main branch and a corresponding sub-branch of the synchronization request content are established, and when the content on the sub-branch is reviewed and approved, the sub-branch is merged into the main branch.

[0026] Optionally, the step S1 specifically includes:

[0027] The article management system creation instruction of the user is obtained, and a user-specific Git repository with the same name is generated according to the article management system name in the article management system creation instruction.

[0028] Optionally, the article management instructions include article creation, article editing and article deletion.

[0029] Optionally, step S3 may be implemented based on a CI / CD tool chain or DevOps.

[0030] According to the above description, the efficiency and quality of content publishing can be improved by integrating / deploying CI / CD tool chains or DevOps in Git.

[0031] In a second aspect, the present invention provides a Git-based article management system implementation system, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the Git-based article management system implementation method of the first aspect is implemented.

[0032] Among them, the technical effects corresponding to the Git-based article management system implementation system provided in the second aspect refer to the relevant description of the Git-based article management system implementation method provided in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A flowchart of a method for implementing a Git-based article management system according to an embodiment of the present invention;

[0034] Figure 2 This is a flow chart of step S1 in the Git-based article management system implementation method according to an embodiment of the present invention;

[0035] Figure 3 This is a flow chart of step S2 in the Git-based article management system implementation method according to an embodiment of the present invention;

[0036] Figure 4 This is a flow chart of step S3 in the Git-based article management system implementation method according to an embodiment of the present invention;

[0037] Figure 5 This is a schematic diagram of the framework of a Git-based article management system implementation system according to an embodiment of the present invention.

[0038] Description of reference numerals:

[0039] 1. Implement the article management system based on Git;

[0040] 2. Processor;

[0041] 3. Memory. DETAILED DESCRIPTION

[0042] In order to better understand the above technical solution, exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a clearer and more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0043] Embodiment 1

[0044] This embodiment is suitable for application scenarios that require article management. Existing content management systems have problems such as complex construction, the need for self-development of content review and version control, and complex backup and migration processes. This embodiment uses the characteristics of Git to manage articles, and can automatically create and manage article content through Git. At the same time, it uses the characteristics of Git to realize article content review, version control, backup and migration. See the following description for details.

[0045] Please refer to Figures 1 to 4 , a method for implementing an article management system based on Git, comprising the steps of:

[0046] S1. Obtain the user's article management system creation instructions, and generate a user-exclusive Git repository according to the article management system creation instructions.

[0047] Wherein, step S1 is specifically as follows:

[0048] Get the user's article management system creation instruction, and generate a user-exclusive Git repository with the same name as the article management system name in the article management system creation instruction.

[0049] Among them, Git is an open source distributed version control system that can effectively and quickly handle version management of projects ranging from very small to very large.

[0050] Reference Figure 2It can be seen that in step S1, the implementation system will provide a user interface, allowing the user to create an article management system belonging to the user through the user interface. The user needs to enter a name as the name of the user's article management system. After successful submission, the background will automatically create a user-exclusive Git repository with the same name on the Git server.

[0051] S2. Obtain the user's article management instructions, and manage the article content for the user's exclusive Git reference according to the article management instructions, wherein the article content is stored in the user's exclusive Git repository in the form of folders and files.

[0052] Among them, article management instructions include article creation, article editing and article deletion, which can add, delete and modify articles.

[0053] Wherein, step S2 comprises the following steps:

[0054] S21. Obtain the user's article classification management instructions, and manage folders under the user's exclusive Git repository according to the article classification management instructions.

[0055] S22. Obtain the user's article content management instructions, and manage files in the folder corresponding to the article category selected by the user in the user's exclusive Git repository according to the article content management instructions.

[0056] Combining step S21 and step S22, it can be seen that this embodiment automatically forms a file and directory structure by taking advantage of the natural advantages of the Git version control system. There is no need to pre-design a complex database structure. Among them, the article exists in the form of a file, and the article can be classified using a folder, and the folder name is the classification name, so that the article content is stored in the form of folders and files in the user's exclusive Git warehouse. Therefore, this embodiment uses the Git warehouse to store articles instead of the database storage solution of the prior art.

[0057] S23. Generate commit content for each management of the article content and record it in the commit record table of the user's exclusive Git repository.

[0058] Reference Figure 3 It can be seen that in step S2, the implementation system provides a user interface, allowing users to manage article content through the user interface, including creating, editing and deleting articles and their categories. The background stores the article content in the created warehouse in the form of folders and files, where each category corresponds to a folder and each article corresponds to a file. Every modification of the article by the user, including additions, deletions and modifications, will be submitted to the warehouse in the form of commit, so every operation will be recorded in the commit record table of the warehouse.

[0059] S3. Obtain the user's article publishing instructions, initiate a synchronization request to the user's exclusive Git repository according to the article publishing instructions, obtain the synchronization request content, perform content review and version control on the synchronization request content through Git branch management and merge requests, and complete the article publishing of the synchronization request content.

[0060] Among them, the content review of the synchronization request content in step S3 includes providing the commit content for review by the reviewer.

[0061] The branch management in step S3 is as follows:

[0062] Establish a main branch and corresponding sub-branch for the synchronization request content. When the content on the sub-branch is reviewed and approved, merge the sub-branch into the main branch.

[0063] Among them, the team members managed by the user-exclusive Git repository can conduct code review and content audit before pushing the content to the main branch, ensuring that all submissions meet the predetermined standards before pushing to the main branch. This process will be recorded in the Git repository, including historical records and version information. Among them, Git's log and diff difference tools help team members track the detailed changes of each submission, including who made which changes and when, thereby improving the transparency and traceability of article content management.

[0064] Reference Figure 4 It can be seen that in step S3, the system provides a user interface, allowing users to publish article content through the user interface. Selecting an article to publish initiates a merge request event for the warehouse. Users with review permissions view the commit content and the notes entered by the user. If they agree to publish, the merge request is approved, and if they disagree, the merge request is rejected. At the same time, the system can set a protection branch, requiring that all submissions must pass the review before they can be merged.

[0065] In addition, Git itself is highly compatible with modern continuous integration / continuous deployment CI / CD tool chains and Devops. Therefore, the CI / CD tool chain or Devops can be integrated into the automated workflow of the above steps in this embodiment to improve the efficiency and quality of content publishing.

[0066] S4. Obtain the user's article backup instructions, copy the user's exclusive Git repository according to the article backup instructions, and generate a user backup Git reference.

[0067] In this embodiment, copying the user-specific Git repository can be achieved by creating a mirror repository or cloning a download repository.

[0068] S5. Obtain the user's article migration instructions, and push the user's exclusive Git repository to other platforms that need to be migrated according to the article migration instructions.

[0069] Therefore, in steps S4 and S5, since the Git repository contains all necessary history records and version information, backup only requires copying the repository, and migration only requires pushing the repository to a new server or platform, which greatly simplifies the backup process and migration process.

[0070] Therefore, this embodiment has the following advantages:

[0071] 1. Improve efficiency: Simplify the construction process, backup process and migration process of the article management system, and improve work efficiency.

[0072] 2. Enhanced collaboration: Utilize the collaborative features of Git to facilitate multiple users to edit and manage article content at the same time.

[0073] 3. Easy to trace: Every management of the article is recorded and backed up, which not only ensures the transparency of article content management, but also facilitates subsequent tracking and recovery.

[0074] 4. Reduce Errors: Automated processes reduce the possibility of human errors.

[0075] Embodiment 2

[0076] Please refer to Figure 5 The Git-based article management system implementation system 1 includes a memory 3, a processor 2, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, the steps in the above-mentioned embodiment 1 are implemented.

[0077] Since the system / device described in the above embodiments of the present invention is a system / device used to implement the method of the above embodiments of the present invention, a person skilled in the art can understand the specific structure and deformation of the system / device based on the method described in the above embodiments of the present invention, and thus will not be described in detail here. All systems / devices used in the method of the above embodiments of the present invention belong to the scope of protection of the present invention.

[0078] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, devices or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0079] The present invention is described with reference to the flowcharts and / or block diagrams of the methods, devices (apparatus) and computer program products according to the embodiments of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions.

[0080] It should be noted that in the claims, any reference numerals placed between brackets shall not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention may be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In the claims enumerating several means, several of these means may be embodied by the same hardware. The use of the words first, second, third, etc., is for convenience of expression only and does not indicate any order. These words may be understood as part of the component name.

[0081] In addition, it should be noted that, in the description of this specification, the description of the terms "one embodiment", "some embodiments", "embodiment", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.

[0082] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments after knowing the basic creative concept. Therefore, the claims should be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present invention.

[0083] Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention should also include these modifications and variations.

Claims

1. A method for implementing an article management system based on Git, characterized in that: Includes steps: S1. Obtain the user's article management system creation instruction, and generate a user-specific Git repository according to the article management system creation instruction; S2. Obtain the user's article management instruction, and manage the article content of the user's exclusive Git reference according to the article management instruction, wherein the article content is stored in the user's exclusive Git repository in the form of folders and files; S3. Obtain the user's article publishing instruction, initiate a synchronization request to the user's exclusive Git repository according to the article publishing instruction, obtain the synchronization request content, perform content review and version control on the synchronization request content through Git branch management and merge requests, and complete the article publishing of the synchronization request content.

2. The method for implementing a Git-based article management system according to claim 1, characterized in that: Also includes the steps: S4. Obtain the user's article backup instruction, copy the user's exclusive Git repository according to the article backup instruction, and generate a user backup Git reference.

3. The method for implementing a Git-based article management system according to claim 1, characterized in that: Also includes the steps: S5. Obtain the user's article migration instructions, and push the user's exclusive Git repository to other platforms that need to be migrated according to the article migration instructions.

4. The method for implementing a Git-based article management system according to any one of claims 1 to 3, characterized in that: The step S2 comprises the following steps: S21, obtaining the user's article classification management instruction, and managing folders under the user's exclusive Git repository according to the article classification management instruction; S22. Obtain the user's article content management instructions, and manage files in the folder corresponding to the article category selected by the user in the user-specific Git repository according to the article content management instructions.

5. The method for implementing a Git-based article management system according to any one of claims 1 to 3, characterized in that: The step S2 further comprises the steps of: S23, generating commit content for each management of the article content, and recording it in the commit record table of the user-specific Git repository; The content review of the synchronization request content in step S3 includes providing the commit content for review by a reviewer.

6. The method for implementing a Git-based article management system according to any one of claims 1 to 3, characterized in that: The branch management in step S3 is as follows: A main branch and a corresponding sub-branch of the synchronization request content are established, and when the content on the sub-branch is reviewed and approved, the sub-branch is merged into the main branch.

7. The method for implementing a Git-based article management system according to any one of claims 1 to 3, characterized in that: The step S1 is specifically as follows: The article management system creation instruction of the user is obtained, and a user-specific Git repository with the same name is generated according to the article management system name in the article management system creation instruction.

8. The method for implementing a Git-based article management system according to any one of claims 1 to 3, characterized in that: The article management instructions include article creation, article editing and article deletion.

9. The method for implementing a Git-based article management system according to any one of claims 1 to 3, characterized in that: The step S3 may be implemented based on a CI / CD tool chain or DevOps.

10. A Git-based article management system implementation system, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for implementing the Git-based article management system according to any one of claims 1 to 9 is implemented.

Images