CN111625221B - Version control method, device, equipment and medium applied to integrated development environment - Google Patents
Version control method, device, equipment and medium applied to integrated development environment Download PDFInfo
- Publication number
- CN111625221B CN111625221B CN202010454452.2A CN202010454452A CN111625221B CN 111625221 B CN111625221 B CN 111625221B CN 202010454452 A CN202010454452 A CN 202010454452A CN 111625221 B CN111625221 B CN 111625221B
- Authority
- CN
- China
- Prior art keywords
- version control
- target
- displaying
- type
- control type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Abstract
The application discloses a version control method and device applied to an integrated development environment, an electronic device and a readable storage medium, wherein the method comprises the following steps: after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data; acquiring a target version control type selected by a user terminal according to the version control interface data; displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control; and submitting the target file to a version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file. According to the application, the version control systems of the same type have the same user interface, and the version control systems of different types have respective unified user interfaces, so that the user can understand and operate more conveniently, and the use experience of the user is improved.
Description
Technical Field
The present application relates to the field of software development, and more particularly, to a version control method and apparatus applied to an integrated development environment, an electronic device, and a computer readable storage medium.
Background
An integrated development environment (IDE, integrated Development Environment) is an application program for providing a program development environment, and generally includes tools such as a code editor, a compiler, a debugger, and a graphical user interface, and is a development software service suite in which a code writing function, an analysis function, a compiling function, a debugging function, and the like are integrated. The version control function is integrated in the better integrated development environment, so that a user can conveniently store and manage the source codes and the resources of the program and realize the change of other information in the development process.
There are two ways in which Visual studio integrates version control, one is plug-in and one is VSPackage. The existence of different version control types in the plug-in mode provides the same interface and the same interface, which is disadvantageous for the integration of different types of version control. For example, git has push functionality whereas SVN does not. The VSPackage mode is customized by a developer, the developed product can only be used on Visual studio, the development difficulty is high, meanwhile, as the version control interface is customized, a user needs to adapt to the customized version control operation flow, different operation flows of the same type of version control are caused, and the experience of the user is influenced. Some integrated development tools have built-in related version control functions, which results in that the related integrated development environment needs to be updated after the version control system is updated, and the subsequent updating is inconvenient.
Therefore, how to solve the above problems is a great concern for those skilled in the art.
Disclosure of Invention
The application aims to provide a version control method, a version control device, an electronic device and a computer readable storage medium applied to an integrated development environment, so that the use experience of a user is improved.
In order to achieve the above object, the present application provides a version control method applied to an integrated development environment, including:
after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data;
acquiring a target version control type selected by a user terminal according to the version control interface data;
displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control;
and submitting the target file to a version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file.
Optionally, after submitting the selected target file to the version control system corresponding to the target version control type, the method further includes:
displaying a menu object representing a version control function under the target version control type;
and receiving a selection instruction of the user terminal for the menu object so as to execute corresponding version control operation.
Optionally, the displaying the menu object characterizing the version control function under the target version control type includes:
and displaying a corresponding menu object representing the version control function by combining the engineering node type corresponding to the currently selected target file and the target version control type.
Optionally, the displaying the menu object characterizing the version control function under the target version control type includes:
and displaying a corresponding menu object representing the version control function by combining the file state information of the currently selected target file and the target version control type.
Optionally, the displaying the menu object characterizing the version control function under the target version control type includes:
sending a request for acquiring a version control menu object to the version control system so that the version control system acquires the menu object representing the version control function from a corresponding version control type interface system according to the target version control type;
and displaying a version control function interface comprising the menu object according to the menu object returned by the version control system.
Optionally, the submitting the target file to the version control system corresponding to the target version control type includes:
according to the target file selected by the user terminal, a submitting request is sent to an action system corresponding to the target version control type;
and calling a client agent corresponding to the target version control type through the action system, and submitting the target file to a version control system corresponding to the target version control type.
To achieve the above object, the present application provides a version control apparatus applied to an integrated development environment, comprising:
the interface display module is used for acquiring and displaying version control interface data after receiving the version control adding instruction;
the version selection module is used for acquiring a target version control type selected by the user terminal according to the version control interface data;
the file selection module is used for displaying the project files existing in the current development environment and receiving the target files which are selected from the project files by the user terminal and need to be subjected to version control;
and the file submitting module is used for submitting the target file to a version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file.
Optionally, the method further comprises:
the menu display module is used for displaying a menu object representing the version control function under the target version control type;
and the object selection module is used for receiving a selection instruction of the user terminal for the menu object so as to execute corresponding version control operation.
To achieve the above object, the present application provides an electronic device including:
a memory for storing a computer program;
a processor for implementing any of the previously disclosed version control methods applied to the integrated development environment when executing the computer program.
To achieve the above object, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of any of the above-disclosed version control methods applied to an integrated development environment.
According to the scheme, the version control method applied to the integrated development environment comprises the following steps: after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data; acquiring a target version control type selected by a user terminal according to the version control interface data; displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control; and submitting the target file to a version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file. According to the application, after the user terminal selects the target version control type and the target file, the target file can be submitted to the version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file, the version control systems of the same type have the same user interface, and the version control systems of different types have respective unified user interfaces, so that the user can understand and operate more conveniently, and the use experience of the user is improved.
The application also discloses a version control device applied to the integrated development environment, an electronic device and a computer readable storage medium, and the technical effects can be realized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a version control method for an integrated development environment according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an interface for adding version control according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an interface for selecting a version control type according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a specific SVN login interface according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a specific creator information interface according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an interface for selecting a target file according to an embodiment of the present application;
FIG. 7 is a flow chart of another version control method for an integrated development environment disclosed in an embodiment of the present application;
fig. 8 and fig. 9 are schematic diagrams of a menu object display interface according to an embodiment of the present application;
FIG. 10 is a block diagram of a version control system for an integrated development environment in accordance with an embodiment of the present application;
FIG. 11 is a block diagram of a version control device for an integrated development environment according to an embodiment of the present application;
fig. 12 is a block diagram of an electronic device according to an embodiment of the present application;
fig. 13 is a block diagram of another electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the related art, when different version control types are integrated by existing integrated development tools, the different version control types provide the same operation flow, and the functions of different version control are confused. Some of the methods are completely customized by developers, so that the inconsistency of products is caused, and the experience of users is influenced. And the related version control function is built in, so that the related integrated development environment needs to be updated after the version control system is updated, and part of the integrated development environment has poor integrated performance.
Therefore, the embodiment of the application discloses a version control method applied to an integrated development environment, which can solve the problem that the same type of version control has different operation flows, and different version control types have the same operation flow.
Referring to fig. 1, a version control method for an integrated development environment according to an embodiment of the present application includes:
s101: after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data;
in the embodiment of the application, the integrated development tool can provide a version control inlet, and a user can issue an additional version control instruction through the version control inlet. Specifically, as shown in fig. 2, the user may pop up a corresponding engineering menu by clicking the engineering node right key of the integrated development tool, including adding a version entry: add to Source Control. When the user clicks the entry, that is, the integrated development tool receives the version control adding instruction, the corresponding version control interface data can be obtained and displayed.
S102: acquiring a target version control type selected by a user terminal according to the version control interface data;
specifically, the version control interface data acquired by the integrated development environment may include information about the version control type, i.e. the type of the integrated version control system may be presented to the user for selection by the user. As shown in FIG. 3, a user may select a desired target version control type, such as SVN, git, etc., via a version control interface.
It should be noted that, after the user terminal selects the target version control type, a subsequent workflow may be performed according to the target version control type. For example, as shown in fig. 4, if the target version control type selected by the user terminal is SVN, the user jumps to the SVN login interface so that the user inputs SVN related information through the interface; as shown in fig. 5, if the target version control type selected by the user terminal is Git, the user jumps to the creator information interface, and the user can input the corresponding name and mailbox information on the interface.
S103: displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control;
in implementations, the user may select a file that needs to be added to the version control. As shown in fig. 6, after the user inputs login information or creator information, the integrated development environment may jump to the file display interface to display the project files existing in the current development environment, and the user may select a target file to be version-controlled from the existing project files.
S104: and submitting the target file to a version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file.
In this step, after the user terminal selects the target file, the integrated development environment may automatically complete the file submission. Specifically, the integrated development environment may send a commit request to an action system corresponding to the target version control type according to the target file selected by the user terminal. The action system further calls a client agent corresponding to the target version control type to submit the target file to the version control system corresponding to the target version control type.
According to the scheme, the version control method applied to the integrated development environment comprises the following steps: after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data; acquiring a target version control type selected by a user terminal according to the version control interface data; displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control; and submitting the target file to a version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file. According to the application, after the user terminal selects the target version control type and the target file, the target file can be submitted to the version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file, the version control systems of the same type have the same user interface, and the version control systems of different types have respective unified user interfaces, so that the user can understand and operate more conveniently, and the use experience of the user is improved.
The embodiment of the application discloses another version control method applied to an integrated development environment, and compared with the previous embodiment, the embodiment further describes and optimizes the technical scheme. See fig. 7 for details:
s201: after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data;
s202: acquiring a target version control type selected by a user terminal according to the version control interface data;
s203: displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control;
s204: submitting the target file to a version control system corresponding to the target version control type;
s205: displaying a menu object representing a version control function under the target version control type;
in the embodiment of the application, after the file is submitted to the version control system, the menu object for representing the version control function under the current version control system, namely the target version control type, can be displayed. Fig. 8 and 9 are respectively a menu object displayed under the SVN version control system and a menu object displayed under the Git version control system.
It should be noted that when the menu object under the target version control type is displayed, the corresponding menu object may be displayed in combination with the engineering node type and the target version control type corresponding to the currently selected target file, for example, the engineering node type may include, but is not limited to, project nodes, application nodes, object nodes, and the like, and the version control function lists corresponding to the engineering tree nodes of different types are also different; or the corresponding menu object can be displayed in combination with the file state information of the currently selected target file and the target version control type, for example, if the file is modified or has conflict, the corresponding displayed version control function list is different; and the corresponding menu object can be displayed by combining the engineering node type, the file state information and the target version control type of the target file.
In an implementation, the process of displaying the menu object under the target version control type may specifically include: the integrated development environment sends a request for acquiring the version control menu object to the version control system, the version control system can acquire the menu object representing the version control function from the corresponding version control type interface system according to the current target version control type, and then the integrated development environment can display a version control function interface comprising the menu object according to the menu object returned by the version control system.
S206: and receiving a selection instruction of the user terminal for the menu object so as to execute corresponding version control operation.
After the menu object under the current version control system is displayed, the user terminal can click on the corresponding menu object according to the service requirement so as to execute the corresponding version control operation.
The following describes a version control system specifically applied to an integrated development environment. In the system, the integrated development environment firstly acquires version control interface data through the version control module and displays the version control interface data, the version control module can respond to user operation and call the version control client module, and the version control client module further calls the version control system to realize final version control operation.
Fig. 10 is a block diagram of the version control system. Referring to fig. 10, the IDE interface system may send a request for obtaining version control interface data to the version control module system, and the version control module system obtains corresponding interface data through the corresponding version control module interface system according to the version control type specified by the request and returns the corresponding interface data to the IDE interface system for display. The version control module interface can respond to user operation and send an operation request to the corresponding version control module action system, the version control module action system can call the corresponding client module through the corresponding client agent, and the client module can forward the operation request to the corresponding version control system, so that corresponding operation is executed.
In the embodiment of the application, the version control types of the same type have unified user interface experience, and the version control types of different types have respective unified user interface experience, so that the product performance is more consistent, and simultaneously, the user can understand the version control types more easily, and the operation is convenient. The corresponding interface of the version control system is directly used, so that higher efficiency can be achieved. In addition, the version control module and the client module are independently arranged, so that the integrated development environment is more stable. Further, version control functions are configured in a plug-in mode, subsequent configuration updating is facilitated, and expandability of the system is improved.
The following describes a version control device applied to an integrated development environment according to an embodiment of the present application, and a version control device applied to an integrated development environment described below and a version control method applied to an integrated development environment described above may be referred to each other.
Referring to fig. 11, a version control device applied to an integrated development environment according to an embodiment of the present application includes:
the interface display module 301 is configured to obtain and display version control interface data after receiving an instruction for adding version control;
the version selection module 302 is configured to obtain a target version control type selected by the user terminal according to the version control interface data;
the file selection module 303 is configured to display an existing project file in a current development environment, and receive a target file that is selected from the project files by the user terminal and needs to be subjected to version control;
and the file submitting module 304 is configured to submit the target file to a version control system corresponding to the target version control type, so as to execute a version control operation corresponding to the target version control type on the target file.
For the specific implementation of the modules 301 to 304, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
On the basis of the foregoing embodiment, as a preferred implementation manner, the version control device provided by the embodiment of the present application may further include:
the menu display module is used for displaying a menu object representing the version control function under the target version control type;
and the object selection module is used for receiving a selection instruction of the user terminal for the menu object so as to execute corresponding version control operation.
The application also provides an electronic device, referring to fig. 12, and the electronic device provided by the embodiment of the application includes:
a memory 100 for storing a computer program;
the processor 200, when executing the computer program, may implement the steps provided in the above embodiments.
Specifically, the memory 100 includes a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer readable instructions, and the internal memory provides an environment for the operating system and the execution of the computer readable instructions in the non-volatile storage medium. The processor 200 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor or other data processing chip in some embodiments, to provide computing and control capabilities for the electronic device, and to implement the steps of the version control method disclosed in any of the foregoing embodiments as applied to the integrated development environment when executing the computer program stored in the memory 100.
On the basis of the above embodiment, as a preferred implementation manner, referring to fig. 13, the electronic device further includes:
an input interface 300, coupled to the processor 200, for obtaining externally imported computer programs, parameters and instructions, which are stored in the memory 100 under control of the processor 200. The input interface 300 may be coupled to an input device for receiving parameters or instructions manually entered by a user. The input device can be a touch layer covered on a display screen, can also be a key, a track ball or a touch pad arranged on a terminal shell, and can also be a keyboard, a touch pad or a mouse, etc.
And a display unit 400 connected to the processor 200 for displaying data processed by the processor 200 and for displaying a visualized user interface. The display unit 400 may be an LED display, a liquid crystal display, a touch-control type liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, or the like.
The network port 500 is connected to the processor 200 and is used for communication connection with external terminal devices. The communication technology adopted by the communication connection can be a wired communication technology or a wireless communication technology, such as a mobile high definition link technology (MHL), a Universal Serial Bus (USB), a High Definition Multimedia Interface (HDMI), a wireless fidelity technology (WiFi), a Bluetooth communication technology with low power consumption, a communication technology based on IEEE802.11s, and the like.
Fig. 13 illustrates only an electronic device having assemblies 100-500, and it will be understood by those skilled in the art that the configuration illustrated in fig. 13 is not limiting of the electronic device and may include fewer or more components than illustrated, or may combine certain components, or a different arrangement of components.
The present application also provides a computer-readable storage medium, which may include: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes. The storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the version control method disclosed in any of the foregoing embodiments as applied to an integrated development environment.
After the user terminal selects the target version control type and the target file, the target file can be submitted to the version control system corresponding to the target version control type so as to execute the version control operation corresponding to the target version control type on the target file, the version control systems of the same type have the same user interface, and the version control systems of different types have respective unified user interfaces, so that the user can understand and operate more conveniently, and the use experience of the user is improved.
In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. For the system disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section. It should be noted that it will be apparent to those skilled in the art that various modifications and adaptations of the application can be made without departing from the principles of the application and these modifications and adaptations are intended to be within the scope of the application as defined in the following claims.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Claims (6)
1. A version control method applied to an integrated development environment, comprising:
after receiving the version control adding instruction, obtaining version control interface data and displaying the version control interface data;
acquiring a target version control type selected by a user terminal according to the version control interface data;
displaying the project files existing in the current development environment, and receiving a target file which is selected from the project files by the user terminal and needs to be subjected to version control;
submitting the target file to a version control system corresponding to the target version control type so as to execute version control operation corresponding to the target version control type on the target file;
after submitting the selected target file to the version control system corresponding to the target version control type, the method further comprises the following steps:
displaying a menu object representing a version control function under the target version control type;
receiving a selection instruction of the user terminal aiming at the menu object so as to execute corresponding version control operation;
the displaying the menu object characterizing the version control function under the target version control type comprises the following steps:
combining the engineering node type corresponding to the currently selected target file and the target version control type, and displaying a corresponding menu object representing the version control function;
the displaying the menu object characterizing the version control function under the target version control type comprises the following steps:
and displaying a corresponding menu object representing the version control function by combining the file state information of the currently selected target file and the target version control type.
2. The version control method according to claim 1, wherein displaying the menu object characterizing the version control function under the target version control type comprises:
sending a request for acquiring a version control menu object to the version control system so that the version control system acquires the menu object representing the version control function from a corresponding version control type interface system according to the target version control type;
and displaying a version control function interface comprising the menu object according to the menu object returned by the version control system.
3. The version control method according to claim 1 or 2, wherein submitting the target file to a version control system corresponding to the target version control type comprises:
according to the target file selected by the user terminal, a submitting request is sent to an action system corresponding to the target version control type;
and calling a client agent corresponding to the target version control type through the action system, and submitting the target file to a version control system corresponding to the target version control type.
4. A version control apparatus for use in an integrated development environment, comprising:
the interface display module is used for acquiring and displaying version control interface data after receiving the version control adding instruction;
the version selection module is used for acquiring a target version control type selected by the user terminal according to the version control interface data;
the file selection module is used for displaying the project files existing in the current development environment and receiving the target files which are selected from the project files by the user terminal and need to be subjected to version control;
the file submitting module is used for submitting the target file to a version control system corresponding to the target version control type so as to execute version control operation corresponding to the target version control type on the target file;
wherein, version control device still includes:
the menu display module is used for displaying a menu object representing the version control function under the target version control type;
the object selection module is used for receiving a selection instruction of the user terminal aiming at the menu object so as to execute corresponding version control operation;
the menu display module is specifically configured to:
combining the engineering node type corresponding to the currently selected target file and the target version control type, and displaying a corresponding menu object representing the version control function;
and displaying a corresponding menu object representing the version control function by combining the file state information of the currently selected target file and the target version control type.
5. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the version control method applied to an integrated development environment according to any one of claims 1 to 3 when executing said computer program.
6. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the version control method of any one of claims 1 to 3 applied to an integrated development environment.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010454452.2A CN111625221B (en) | 2020-05-26 | 2020-05-26 | Version control method, device, equipment and medium applied to integrated development environment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010454452.2A CN111625221B (en) | 2020-05-26 | 2020-05-26 | Version control method, device, equipment and medium applied to integrated development environment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111625221A CN111625221A (en) | 2020-09-04 |
CN111625221B true CN111625221B (en) | 2023-09-29 |
Family
ID=72259985
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010454452.2A Active CN111625221B (en) | 2020-05-26 | 2020-05-26 | Version control method, device, equipment and medium applied to integrated development environment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111625221B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112148354B (en) * | 2020-09-27 | 2023-07-25 | 网易(杭州)网络有限公司 | Game starting method and device |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001082066A1 (en) * | 2000-04-21 | 2001-11-01 | Togethersoft Corporation | Diagrammatic control of software in a version control system |
CN101430643A (en) * | 2007-11-05 | 2009-05-13 | 国际商业机器公司 | Method and apparatus for providing item development environment, and item development system |
CN108319466A (en) * | 2017-12-15 | 2018-07-24 | 北京先进数通信息技术股份公司 | A kind of restoration methods and device of configuration information |
CN108376065A (en) * | 2018-03-01 | 2018-08-07 | 中国航空无线电电子研究所 | The system for building the avionics software development environment of model-driven |
CN108920137A (en) * | 2018-07-01 | 2018-11-30 | 甘肃万维信息技术有限责任公司 | A kind of system of creation web project and code based on eclipse frame |
CN109117180A (en) * | 2018-09-28 | 2019-01-01 | 中国银行股份有限公司 | A kind of integrated method and device of program |
CN109522025A (en) * | 2018-10-30 | 2019-03-26 | 深圳市小赢信息技术有限责任公司 | A kind of code delivery system based on git |
CN109656618A (en) * | 2018-12-13 | 2019-04-19 | 泰康保险集团股份有限公司 | Source code edition control method, configuration server, medium, electronic equipment |
WO2019153013A1 (en) * | 2018-02-05 | 2019-08-08 | Codestream, Inc. | Systems and methods for providing an instant communication channel within integrated development environments |
WO2020088344A1 (en) * | 2018-10-31 | 2020-05-07 | 北京数聚鑫云信息技术有限公司 | Api version control method, apparatus, device, and medium |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8352445B2 (en) * | 2008-05-23 | 2013-01-08 | Microsoft Corporation | Development environment integration with version history tools |
-
2020
- 2020-05-26 CN CN202010454452.2A patent/CN111625221B/en active Active
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001082066A1 (en) * | 2000-04-21 | 2001-11-01 | Togethersoft Corporation | Diagrammatic control of software in a version control system |
CN101430643A (en) * | 2007-11-05 | 2009-05-13 | 国际商业机器公司 | Method and apparatus for providing item development environment, and item development system |
CN108319466A (en) * | 2017-12-15 | 2018-07-24 | 北京先进数通信息技术股份公司 | A kind of restoration methods and device of configuration information |
WO2019153013A1 (en) * | 2018-02-05 | 2019-08-08 | Codestream, Inc. | Systems and methods for providing an instant communication channel within integrated development environments |
CN108376065A (en) * | 2018-03-01 | 2018-08-07 | 中国航空无线电电子研究所 | The system for building the avionics software development environment of model-driven |
CN108920137A (en) * | 2018-07-01 | 2018-11-30 | 甘肃万维信息技术有限责任公司 | A kind of system of creation web project and code based on eclipse frame |
CN109117180A (en) * | 2018-09-28 | 2019-01-01 | 中国银行股份有限公司 | A kind of integrated method and device of program |
CN109522025A (en) * | 2018-10-30 | 2019-03-26 | 深圳市小赢信息技术有限责任公司 | A kind of code delivery system based on git |
WO2020088344A1 (en) * | 2018-10-31 | 2020-05-07 | 北京数聚鑫云信息技术有限公司 | Api version control method, apparatus, device, and medium |
CN109656618A (en) * | 2018-12-13 | 2019-04-19 | 泰康保险集团股份有限公司 | Source code edition control method, configuration server, medium, electronic equipment |
Also Published As
Publication number | Publication date |
---|---|
CN111625221A (en) | 2020-09-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110837369A (en) | Form generation method and device, electronic equipment and storage medium | |
US9195522B2 (en) | Method and device for controlling communication between applications in a web runtime environment | |
EP3605324A1 (en) | Application development method and tool, device, and storage medium thereof | |
CN110851114A (en) | Business system development method and device, electronic equipment and storage medium | |
US20170359701A1 (en) | Sticker distribution system for messaging apps | |
US9934007B2 (en) | Method for operating tool in working environment and machine using such method | |
JP2018528559A (en) | Method and system for realizing data tracking by software development kit | |
CN1684034A (en) | Application of data-binding mechanism to perform command binding | |
CN107656729B (en) | List view updating apparatus, method and computer-readable storage medium | |
CN104731589A (en) | Automatic generation method and device of user interface (UI) | |
US20160154644A1 (en) | Real-time previewing and modifying an application under development | |
CN109445841B (en) | Interface document management method, device, server and storage medium | |
US9038019B2 (en) | Paige control for enterprise mobile applications | |
US8413109B2 (en) | Systems and methods for metamodel transformation | |
CN108776587B (en) | Data acquisition method and device, computer equipment and storage medium | |
KR102428166B1 (en) | Item maps for app store apps | |
CN111736818A (en) | Application creation method and device based on container cloud, electronic equipment and storage medium | |
CN111625221B (en) | Version control method, device, equipment and medium applied to integrated development environment | |
WO2014120227A1 (en) | Remotely executing operations of an application using a schema that provides for executable scripts in a nodal hierarchy | |
US11853727B2 (en) | Group control and management among electronic devices | |
CN111831320A (en) | Plug-in management method and device, electronic equipment and storage medium | |
Schuler et al. | Rule-based generation of mobile user interfaces | |
CN111766987B (en) | Application program management method and device and electronic equipment | |
CN114546410A (en) | Code optimization method based on design mode and related equipment | |
CN113296772A (en) | Page configuration method and device, computer equipment and readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |