Application method for management authority of code repository, electronic equipment, medium and product
By querying personnel change information in the code repository management system, information for requesting permissions from the updated administrator is generated, which solves the problem of administrator query errors and ensures the accuracy of permission requests and timely updates of management files.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CONTINENTAL SMART CORE TECH (SHANGHAI) CO LTD
- Filing Date
- 2025-12-22
- Publication Date
- 2026-05-08
AI Technical Summary
In code repository management, the administrator information retrieved by the user is incorrect, making it impossible to correctly apply for management permissions.
By receiving the identifier information of the code repository and querying personnel change information, the system generates information to request permissions from the updated administrator, ensuring the accuracy of permission requests.
This avoids errors in administrator queries caused by personnel changes, ensures the accuracy of permission requests, and reduces the burden of manual maintenance.
Smart Images
Figure CN121997353A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a method, electronic device, medium, and product for applying for code repository management permissions. Background Technology
[0002] To facilitate code management and development, developers upload their code to code management platforms (such as GitHub, GitLab, etc.) for management. For example... Figure 1 As shown, developers can upload their developed program code to the code management platform's code repository on server 200 via electronic device 100 for management. Each code repository has at least one administrator.
[0003] To ensure the security of the code repository, other developers need to apply for administrative privileges from the repository administrator before they can operate on the program code stored in the repository, such as modifying, copying, or updating it.
[0004] To facilitate users' requests for code repository management permissions, some electronic devices can automatically query the repository administrator based on the user's input of the repository's path, name, type, etc., eliminating the need for manual querying. However, in some cases, the electronic device may query an incorrect repository administrator, leading to an incorrect recipient for the code repository management permission request, thus preventing the user from obtaining management permissions for that repository. Summary of the Invention
[0005] This application provides a method, electronic device, medium, and product for applying for code repository management permissions, which solves the problem that users cannot apply for code repository management permissions because the administrator of the code repository they query is incorrect.
[0006] In a first aspect, embodiments of this application provide a method for applying for code repository management permissions, applied to an electronic device. The method includes: receiving identification information of a target code repository; querying personnel change information corresponding to the target code repository based on the identification information, wherein the personnel change information indicates that the administrator of the target code repository has been updated from a first administrator to a second administrator; and generating permission application information for the target code repository based on the personnel change information, wherein the permission application information is used to apply to the second administrator for management permissions of the target code repository.
[0007] After receiving the identification information of the target code repository, the electronic device queries the personnel change information corresponding to the target code repository based on the identification information. If the personnel change information indicates that the administrator of the target code repository has been updated from the first administrator to the second administrator, the device generates the permission request information for the target code repository based on the personnel change information to request management permissions for the target code repository from the second administrator. This can avoid the problem of querying the wrong administrator of the target code repository due to personnel changes, thereby preventing users from being unable to request management permissions for the target code repository from the correct administrator.
[0008] In some embodiments, generating permission request information for the target code repository based on personnel change information includes: querying the account information of the second administrator; and generating permission request information based on the identification information and the account information of the second administrator.
[0009] After the electronic device detects that the administrator of the target code repository has changed from the first administrator to the second administrator based on personnel change information, the device can query the second administrator's account information. Then, based on the target code repository's identifier and the second administrator's account information, it generates permission request information to request management permissions for the target code repository from the second administrator. Generating permission request information based on the target code repository's identifier and the second administrator's account information ensures the accuracy of the permission request information, such as the requesting target and the code repository to be requested.
[0010] In some embodiments, account information includes account name and / or account number.
[0011] Generating permission request information for the target code repository based on the second administrator's username and / or account number ensures the accuracy of the requested objects in the generated permission request information.
[0012] In some embodiments, before querying the personnel change information of the target code repository based on the identification information, the process includes: querying the first repository information of the target code repository from the code repository management file based on the identification information, wherein the first repository information indicates that the administrator of the target code repository is the first administrator.
[0013] By correcting the query results of code repository management files through personnel change information queries, the accuracy of the query results for the target code repository administrator can be ensured, thereby avoiding errors in the permission request information for the target code repository generated by electronic devices.
[0014] In some embodiments, the method further includes: updating the first repository information to second repository information, wherein the second repository information indicates that the administrator of the target code repository is a second administrator.
[0015] Updating code repository management files based on query results of personnel change information enables timely updates to code repository management files and reduces the burden of manual maintenance.
[0016] In some embodiments, the identification information includes path address, warehouse name, warehouse number and / or warehouse type.
[0017] In some embodiments, personnel change information includes personnel departure handover information or personnel transfer handover information.
[0018] By querying employee departure and handover information to determine the administrator of the target code repository, it is possible to avoid errors in querying the target code repository administrator due to employee departure. This also prevents electronic devices from generating incorrect permission request information for the target code repository, thus preventing users from being unable to obtain management permissions for the target code repository.
[0019] By querying personnel transfer information to determine the administrator of the target code repository, it is possible to avoid errors in querying the target code repository administrator due to personnel transfer. This also prevents electronic devices from generating incorrect permission request information for the target code repository, thus avoiding situations where users are unable to obtain management permissions for the target code repository.
[0020] Secondly, embodiments of this application provide an electronic device, including: a memory for storing instructions; and a processor, which, when executing the instructions in the memory, causes the electronic device to perform the method described in the first aspect of this application. The beneficial effects achievable in this second aspect can be found in the beneficial effects of the method provided in the first aspect embodiment, and will not be repeated here.
[0021] Thirdly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method provided in the first aspect of the embodiment. The beneficial effects achievable in this third aspect can be referenced to the beneficial effects of the methods provided in the first or second aspect of the embodiment, and will not be repeated here.
[0022] Fourthly, embodiments of this application provide a computer program product containing program code that, when executed by a computer or processor, causes the computer or processor to perform the method provided in the first aspect embodiment. The beneficial effects achievable in this fourth aspect can be found in the beneficial effects of the method provided in the first aspect embodiment, and will not be repeated here.
[0023] Fifthly, this application provides a device for applying for code repository management permissions, comprising a receiving module, a querying module, and a generating module. The receiving module receives identification information of a target code repository; the querying module, based on the identification information, queries personnel change information corresponding to the target code repository, wherein the personnel change information indicates that the administrator of the target code repository has been updated from a first administrator to a second administrator; the generating module, based on the personnel change information, generates permission application information for the target code repository, wherein the permission application information is used to apply for management permissions for the target code repository from the second administrator. The beneficial effects achievable in this fifth aspect are similar to those of the method provided in the first aspect embodiment, and will not be repeated here. Attached Figure Description
[0024] Figure 1 According to some embodiments of this application, a scenario example diagram is shown;
[0025] Figure 2A According to some embodiments of this application, an example diagram of a warehouse permission management interface is shown;
[0026] Figure 2B According to some embodiments of this application, an example diagram of another warehouse permission management interface is shown;
[0027] Figure 2C According to some embodiments of this application, an example diagram of yet another warehouse access control interface is shown;
[0028] Figure 2D According to some embodiments of this application, an example diagram of another warehouse permission management interface is shown;
[0029] Figure 3 According to some embodiments of this application, a schematic diagram of applying for management permissions for a code repository is shown;
[0030] Figure 4 According to some embodiments of this application, an example diagram of an interface containing employee departure handover information is shown;
[0031] Figure 5 According to some embodiments of this application, an example diagram of an interface containing personnel transfer and handover information is shown;
[0032] Figure 6 According to some embodiments of this application, a flowchart illustrating a method for applying for code repository management permissions is shown;
[0033] Figure 7 According to some embodiments of this application, an example diagram of another warehouse permission management interface is shown;
[0034] Figure 8 According to some embodiments of this application, a flowchart illustrating another method for applying for code repository management permissions is shown;
[0035] Figure 9 According to some embodiments of this application, a flowchart of an application for code repository management permissions is shown;
[0036] Figure 10 According to some embodiments of this application, a schematic diagram of the structure of a code repository management permission application device is shown;
[0037] Figure 11 According to some embodiments of this application, a schematic diagram of the structure of another code repository management permission application device is shown;
[0038] Figure 12 According to some embodiments of this application, a schematic diagram of the structure of an electronic device is shown. Detailed Implementation
[0039] The illustrative embodiments of this application include, but are not limited to, methods for applying for code repository management permissions, electronic devices, media, and products.
[0040] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be described in detail below with reference to the accompanying drawings and specific implementation methods.
[0041] The method provided in this application can be applied to any electronic device, including but not limited to mobile stations (MS) and mobile terminals (MT). For example, the electronic device can be a mobile phone, smart TV, wearable device, tablet computer, desktop computer, laptop computer, virtual reality (VR) device, augmented reality (AR) device, terminal in industrial control, terminal in self-driving, terminal in remote medical surgery, terminal in smart grid, terminal in transportation safety, terminal in smart city, terminal in smart home, etc. This application does not limit the specific form of the electronic device. The following description uses a computer as an example.
[0042] Figure 2AAccording to some embodiments of this application, an example diagram of a warehouse permission management interface is shown. Figure 2B According to some embodiments of this application, an example diagram of another warehouse permission management interface is shown. Figure 2C According to some embodiments of this application, an example diagram of yet another warehouse permission management interface is shown. Figure 2D According to some embodiments of this application, an example diagram of another warehouse permission management interface is shown.
[0043] like Figures 2A to 2D As shown, an electronic device 100 (using a computer as an example) has a management application installed, and user A's account is logged into the management application. When user A opens the code repository permission management interface 10 of the management application and clicks the application control 11 on the interface 10, the electronic device 100 displays window 12. After user A enters the path address of code repository A (e.g., address 1: xxxxxxx) in the code repository path input field L1 of window 12, the management application of the electronic device 100 can query the administrator information of code repository A from the code repository management file. The code repository management file is a file that stores code repository information. The code repository information includes the code repository's path address, type, name, and other identifying information, as well as the code repository's administrator information.
[0044] For example, Table 1 below shows the repository information for each code repository where the code repository file is stored.
[0045] Table 1
[0046]
[0047] As shown in Table 1, code repository A has repository number 56, path address 1, repository type "project" (representing a project repository), and administrator user B. Code repository B has repository number 55, path address 2, repository type "project," and administrator user C. Code repository C has repository number 54, path address 3, repository type "group" (representing a group repository), and administrator user D. Code repository D has repository number 53, path address 4, repository type "project," and administrator user E. Code repository E has repository number 52, path address 5, repository type "project," and administrator user A.
[0048] After the user enters the address 1 of code repository A in the code repository path input field L1 of window 12, the management application can use the address 1 of code repository A entered by the user to query from Table 1 above that the administrator of code repository A is user B. Then, it automatically enters user B's account name in the administrator input field L2 of window 12. Then, when user A clicks the submit control K2 in window 12, the management application can respond to the click operation of control K2, close window 12, generate permission request information for requesting management permissions for code repository A from user B, and display the prompt message 13 "Submitted for approval" to indicate that user A has initiated a request for management permissions for code repository A from user B.
[0049] Figure 3 According to some embodiments of this application, a schematic diagram of applying for management permissions for a code repository is shown.
[0050] like Figure 3 As shown, in response to receiving the path address of code repository A input by user A, the management application queries the code repository files based on the path address and finds that the administrator of code repository A is user B. The management application then initiates an approval process with user B as the applicant, requesting management permissions for code repository A from user B.
[0051] In some embodiments, the repository information stored in the code repository management file is maintained and updated by the relevant developers. If User B has left the company or changed positions and is no longer responsible for managing code repository A, transferring the management rights of code repository A to User C, but the repository information of code repository A stored in the code repository management file is not updated in a timely manner, then when User A enters the path address of code repository A on the code repository permission management interface 10, the management application will still find User B as the administrator of code repository A, instead of User C. This will cause User A to mistakenly request management rights for code repository A from User B, but User B has left the company and cannot approve the request, thus User A will not be able to obtain management rights for code repository A.
[0052] In view of this, this application provides a method for managing code permissions. The electronic device, based on the received identifier information of the target code repository, queries the personnel change information corresponding to the target code repository. When the queried personnel change information indicates that the administrator of the target code repository has been updated from a first administrator to a second administrator, permission request information is generated to request management permissions for the target code repository from the second administrator. It can be understood that determining the administrator of the target code repository by querying personnel change information can avoid the problem of incorrect administrators being queried due to personnel changes, thereby preventing users from being unable to request management permissions for the target code repository from the correct administrator.
[0053] It is understandable that the target code repository is the code repository for which administrative permissions are to be requested, such as the aforementioned code repository A.
[0054] In some embodiments, the identification information includes, but is not limited to, path address, warehouse name, warehouse number and / or warehouse type.
[0055] In some embodiments, personnel change information includes personnel departure handover information or personnel transfer handover information.
[0056] It's understandable that employee departure handover information refers to the information submitted by the employee upon leaving the company, indicating the transfer of management permissions for the code repository. Similarly, employee transfer handover information refers to the information submitted by the employee upon transferring to a new role, indicating the transfer of management permissions for the code repository.
[0057] For example, Figure 4 According to some embodiments of this application, an example diagram of an interface containing employee departure handover information is shown.
[0058] like Figure 4 As shown, the screen of electronic device 100 displays a code repository handover interface 20 for the management application. The code repository handover interface 20 displays the name of the departing employee (e.g., User B), the handover status (e.g., "handover completed"), detailed data of the code repository (e.g., the path address and name of code repository A), and the name of the new administrator of the code repository to be handed over (e.g., User C). From the departure handover information displayed on the code repository handover interface 20, it can be seen that User B has transferred the management rights of code repository A to User C.
[0059] For example, Figure 5 According to some embodiments of this application, an example diagram of an interface containing personnel transfer and handover information is shown.
[0060] like Figure 5 As shown, the screen of electronic device 100 displays a code repository handover interface 30 for the management application. The code repository handover interface 30 displays the name of the employee transferring (e.g., User B), the handover status (e.g., already handed over), detailed data of the code repository (e.g., the path address and name of code repository A), and the name of the new administrator of the code repository to be handed over (e.g., User C). From the handover information displayed on the code repository handover interface 20, it can be seen that User B has transferred the management rights of code repository A to User C.
[0061] The following section, with reference to specific flowcharts, describes the method for applying for code repository management permissions provided in this application embodiment.
[0062] Figure 6 According to some embodiments of this application, a flowchart illustrating a method for applying for code repository management permissions is shown. The various steps of this method are executed by electronic devices, and will not be described in detail below.
[0063] like Figure 6 As shown, the process includes:
[0064] S101: Received the identification information of the target code repository.
[0065] In some embodiments, the management application of the electronic device receives the identification information of the target code repository input by the user. It is understood that the management application is used to manage code repositories and personnel change information.
[0066] For example, Figure 7 According to some embodiments of this application, an example diagram of another warehouse permission management interface is shown. Figure 7 As shown, the management application of electronic device 100 receives the path address of code repository A (as the target code repository) entered by user A in the code repository path input field L1 of window 12, such as address 1: xxxxxxxx.
[0067] S102: Based on the identification information, query the personnel change information corresponding to the target code repository, wherein the personnel change information indicates that the administrator of the target code repository has been updated from the first administrator to the second administrator.
[0068] In some embodiments, the electronic device stores personnel change information, for example... Figure 4 The personnel departure handover information shown, or, Figure 5 The personnel transfer information shown.
[0069] In some embodiments, the management application of the electronic device queries the target code repository based on the identification information of the target code repository and finds that there is a corresponding personnel change information in the target code repository. The personnel change information indicates that the identification information of the target code repository is updated from the first administrator to the second administrator.
[0070] For example, the management application of electronic device 100 queries the path address of code repository A. Figure 4 The resignation handover information submitted by User B is shown, which instructs the administrator of code repository A to be updated from User B (as the first administrator) to User C (as the second administrator).
[0071] For example, the management application for electronic device 100 queries the path address of code repository A. Figure 5 The transfer information submitted by User B is shown below. This transfer information instructs the administrator of code repository A to update from User B to User C.
[0072] S103: Based on the personnel change information, generate permission request information for the target code repository, wherein the permission request information is used to request management permissions for the target code repository from the second administrator.
[0073] In some embodiments, the electronic device can query the account information of the second administrator, and then generate permission request information for the target code repository based on the identifier information of the target code repository and the account information of the second administrator.
[0074] In some embodiments, account information includes account name and / or account number.
[0075] For example, such as Figure 7 As shown, after the management application of electronic device 100 detects that the administrator of code repository A has been updated from user B to user C, the management application can query user C's account name and populate it into the administrator input field L2. Then, in response to the user clicking the submit control K2 in window 12, the management application generates permission request information for code repository A based on the path address of code repository A and user C's account name. This permission request information is used to request management permissions for code repository A from user C.
[0076] In this embodiment, after receiving the identification information of the target code repository, the electronic device queries the personnel change information of the target code repository based on the identification information. When the personnel change information indicates that the administrator of the target code repository has been updated from the first administrator to the second administrator, it generates permission application information to request management permissions of the target code repository from the second administrator. Instead of determining the administrator of the target code repository by querying the code repository management file managed by the relevant personnel, it can avoid the problem of incorrect query of the administrator of the target code repository due to personnel changes (such as resignation or job transfer). This can avoid the generation of incorrect permission application information for the target code repository, which would prevent the user from being unable to apply for management permissions of the target code repository.
[0077] Figure 8 According to some embodiments of this application, a flowchart illustrating another method for applying for code repository management permissions is shown. The various steps of this method are executed by an electronic device, and will not be described in detail below.
[0078] like Figure 8 As shown, the process includes:
[0079] S201: Received the identification information of the target code repository.
[0080] S201 and S101 are essentially the same, and will not be described again here.
[0081] S202: Based on this identification information, retrieve the first repository information of the target code repository from the code repository management file, wherein the first repository information indicates that the administrator of the target code repository is the first administrator.
[0082] In some embodiments, after the management application of the electronic device receives the identification information of the target code repository, the management application queries the first repository information of the target code from the code repository management file based on the identification information, and the first repository information indicates that the administrator of the target code repository is the first administrator.
[0083] For example, the information for the first repository could be the information stored in the first row of Table 1 above. The management application could then use the address 1 of code repository A entered by the user to query Table 1 and find that the administrator of code repository A is user B.
[0084] S203: Based on the identification information, the personnel change information corresponding to the target code repository is retrieved, wherein the personnel change information indicates that the administrator of the target code repository has been updated from the first administrator to the second administrator.
[0085] S203 and S102 are essentially the same, and will not be described in detail here.
[0086] S204: Based on the personnel change information, generate permission request information for the target code repository, wherein the permission request information is used to request management permissions for the target code repository from the second administrator.
[0087] S204 and S103 are essentially the same, and will not be elaborated further here.
[0088] S205: Update the first repository information to the second repository information, wherein the second repository information indicates that the administrator of the target code repository is the second administrator.
[0089] In some embodiments, after the management application of the electronic device generates permission request information for the target code repository, the management application can update the first repository information in the code repository management file to the second repository information.
[0090] For example, the second warehouse information can be the information stored in the first row of Table 2 below, that is, the management application can update Table 1 above to Table 2 below.
[0091] Table 2
[0092]
[0093] As shown in Table 2, the administrator of code repository A was changed from user B to user C.
[0094] In this embodiment, the electronic device corrects the query results of the administrator query on the code repository management file by querying personnel change information, which can ensure the accuracy of the administrator query on the code repository. Furthermore, updating the code repository management file based on the query results of personnel change information can ensure that the code repository management file is updated in a timely manner and can reduce the burden of manual maintenance.
[0095] Figure 9 According to some embodiments of this application, a flowchart of an application for code repository management permissions is shown.
[0096] like Figure 9 As shown, after the management application receives the path address of code repository A from the user, it queries the code repository management files (e.g., Table 1 above) to find that the administrator of code repository A is user B. Then, based on the path address of code repository A, the management application queries the personnel change information corresponding to code repository A, for example... Figure 4 The handover information shown is or Figure 5 The transfer and handover information shown indicates that the administrator of code repository A has changed from user B to user C. The management application generates a request for management permissions for code repository A from user C and initiates an approval process. Then, the management application updates the code repository management files, changing the administrator of code repository A from user B to user C, for example, updating Table 1 above to Table 2 above.
[0097] In order to implement the code repository management permission application method provided in the embodiments of this application, this application proposes a code repository management permission application device. Figure 10 According to some embodiments of this application, a schematic diagram of a device for applying for code repository management permissions is shown. It is understood that the device for applying for code repository management permissions can be a hardware device or a software device, and there is no limitation thereto.
[0098] like Figure 10 As shown, the code repository management permission application device 200 includes a receiving module 210, a query module 220, and a generation module 230.
[0099] The receiving module 210 is used to receive the identification information of the target code repository.
[0100] The query module 220 is used to query the personnel change information corresponding to the target code repository based on the identification information. The personnel change information indicates that the administrator of the target code repository has been updated from the first administrator to the second administrator.
[0101] The generation module 230 is used to generate permission request information for the target code repository based on personnel change information. The permission request information is used to request management permissions for the target code repository from the second administrator.
[0102] In some embodiments, the generation module 230 is further configured to query the account information of the second administrator and generate permission request information for the target code repository based on the identification information of the target code repository and the account information of the second administrator.
[0103] In some embodiments, the query module 220 is further configured to query the first repository information of the target code repository from the code repository management file based on the identifier information of the target code repository before querying the personnel change information of the target code repository based on the identifier information of the target code repository, wherein the first repository information indicates that the administrator of the target code repository is the first administrator.
[0104] It should be noted that the information interaction and execution process between the modules of the above-mentioned code repository management permission application device 200 are based on the same concept as the method embodiment of this application, and the resulting technical effects are the same as those of the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in this application, and will not be repeated here.
[0105] Figure 11 According to some embodiments of this application, a schematic diagram of the structure of another code repository management permission application device is shown.
[0106] like Figure 11 As shown, the code repository management permission application device 200 also includes an update module 240. The update module 240 is used to update the first repository information to the second repository information, wherein the second repository information indicates that the administrator of the target code repository is the second administrator.
[0107] It should be noted that the information interaction and execution process between the modules of the above-mentioned code repository management permission application device 200 are based on the same concept as the method embodiment of this application, and the resulting technical effects are the same as those of the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in this application, and will not be repeated here.
[0108] Figure 12 According to some embodiments of this application, a schematic diagram of an electronic device is shown. This electronic device is used to implement the code repository management permission application method provided in the foregoing embodiments.
[0109] like Figure 12As shown, the electronic device 100 includes one or more processors 101, system memory 102, non-volatile memory (NVM) 103, communication interface 104, input / output device 105, and system control logic unit 106 for coupling the processor 101, system memory 102, NVM 103, communication interface 104, and input / output device 105. Wherein:
[0110] Processor 101 may include one or more processing units, such as processing modules or processing circuits that may include a central processing unit (CPU), graphics processing unit (GPU), digital signal processor (DSP), micro-programmed control unit (MCU), artificial intelligence (AI) processor or field programmable gate array (FPGA), neural network processing unit (NPU), etc., and may include one or more single-core or multi-core processors.
[0111] System memory 102 is volatile memory, such as random-access memory (RAM), double data rate synchronous dynamic random access memory (DDR SDRAM), etc. System memory is used for temporary storage of data and / or instructions. For example, in some embodiments, system memory 102 can be used to store the aforementioned object code, executable files, executable instructions, etc., and can also be used to store instructions for the vehicle control methods provided in the aforementioned embodiments.
[0112] The non-volatile memory 103 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. In some embodiments, the non-volatile memory 103 may include any suitable non-volatile memory and / or any suitable non-volatile storage device, such as a hard disk drive (HDD), compact disc (CD), digital versatile disc (DVD), solid-state drive (SSD), etc. In some embodiments, the non-volatile memory 103 may also be a removable storage medium, such as a secure digital (SD) memory card. In other embodiments, the non-volatile memory 103 may be used to store instructions for the vehicle control methods provided in the foregoing embodiments.
[0113] Specifically, system memory 102 and non-volatile memory 103 may each include a temporary copy and a permanent copy of instruction 107. Instruction 107 may include, when executed by at least one of processors 101, causing electronic device 100 to implement the vehicle control method provided in the embodiments of this application.
[0114] The communication interface 104 may include a transceiver for providing a wired or wireless communication interface for the electronic device 100, thereby enabling communication with any other suitable device via one or more networks. In some embodiments, the communication interface 104 may be integrated into other components of the electronic device 100, for example, the communication interface 104 may be integrated into the processor 101. In some embodiments, the electronic device 100 may communicate with other devices through the communication interface 104, for example, the electronic device 100 may obtain required data from other electronic devices through the communication interface 104.
[0115] Input / output device 105 can be an input device such as a keyboard or mouse, or an output device such as a monitor. Users can interact with electronic device 100 through input / output device 105.
[0116] The system control logic unit 106 may include any suitable interface controller to provide any suitable interface to other modules of the electronic device 100. For example, in some embodiments, the system control logic unit 106 may include one or more memory controllers to provide an interface to the system memory 102 and the non-volatile memory 103.
[0117] In some embodiments, at least one of the processors 101 may be packaged together with the logic of one or more controllers for the system control logic unit 106 to form a system in package (SiP). In other embodiments, at least one of the processors 101 may also be integrated on the same chip with the logic of one or more controllers for the system control logic unit 106 to form a system-on-chip (SoC).
[0118] Understandable. Figure 12 The structure of the electronic device 100 shown is merely an example. In other embodiments, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0119] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods provided in the foregoing embodiments.
[0120] This application also provides a computer program product containing program code that, when executed by a computer or processor, causes the computer or processor to perform the methods provided in the foregoing embodiments.
[0121] Various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.
[0122] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor, a microcontroller, an application-specific integrated circuit, or a microprocessor.
[0123] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.
[0124] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried on or stored thereon by one or more transient or non-transitory machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media can include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, compact disc-read-only memory (CD-ROMs), magneto-optical disks, read-only memory (ROM), random-access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagation signals. Therefore, machine-readable media includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.
[0125] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Furthermore, the inclusion of structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.
[0126] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problems proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.
[0127] It should be noted that in the examples and description of this application, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0128] Although this application has been illustrated and described with reference to certain preferred embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made thereto without departing from the scope of this application.
Claims
1. A method for applying for code repository management permissions, characterized in that, Applied to electronic devices, the method includes: Received the identification information of the target code repository; Based on the identification information, the personnel change information corresponding to the target code repository is retrieved, wherein the personnel change information indicates that the administrator of the target code repository has been updated from the first administrator to the second administrator; Based on the personnel change information, permission request information for the target code repository is generated, wherein the permission request information is used to request management permissions for the target code repository from the second administrator.
2. The method according to claim 1, characterized in that, The step of generating permission request information for the target code repository based on the personnel change information includes: Query the account information of the second administrator; The permission request information is generated based on the identification information and the account information of the second administrator.
3. The method according to claim 2, characterized in that, The account information includes the account name and / or account number.
4. The method according to claim 1, characterized in that, Before retrieving personnel change information for the target code repository based on the identification information, the process includes: Based on the identification information, the first repository information of the target code repository is retrieved from the code repository management file, wherein the first repository information indicates that the administrator of the target code repository is the first administrator.
5. The method according to claim 4, characterized in that, The method further includes: The first repository information is updated to the second repository information, wherein the second repository information indicates that the administrator of the target code repository is the second administrator.
6. The method according to any one of claims 1 to 5, characterized in that, The identification information includes path address, warehouse name, warehouse number and / or warehouse type.
7. The method according to any one of claims 1 to 5, characterized in that, The personnel change information includes personnel departure handover information or personnel transfer handover information.
8. An electronic device, characterized in that, include: Memory, used to store instructions; A processor, when executing instructions in the memory, can cause the electronic device to perform the code repository management permission application method according to any one of claims 1 to 7.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method for applying for code repository management permissions as described in any one of claims 1 to 7.
10. A computer program product, characterized in that, The program code contained in the computer program product, when executed by a computer or processor, causes the computer or processor to perform the method for applying for code repository management permissions as described in any one of claims 1 to 7.