Dynamic review of software updates after pull requests

Patent metadata

Field	Value
Publication number	US-11537392-B2
Application number	US-202117140748-A
Country	US
Kind code	B2
Filing date	Jan 4, 2021
Priority date	Jan 4, 2021
Publication date	Dec 27, 2022
Grant date	Dec 27, 2022

Abstract

In some implementations, a system may receive, from a software repository, a difference file indicating changes, to software code, that was submitted to the software repository. The system may parse the difference file to determine files, associated with the software code, affected by the changes and to determine content associated with the changes. The system may apply rules, from a rule dictionary, based on comparing identifiers, associated with the files, with identifiers included in the rules and based on comparing the content, associated with the changes, with content included in the rules. The system may generate software review checklist items based on applying the rules and output the software review checklist items for display. The system may receive, based on input from a user, confirmation of the changes and commit the changes to the software repository based on the confirmation.

First claim

What is claimed is:

1. A computer-implemented method of rule-based review of software code changes, comprising:
receiving, from a software repository, a difference file indicating at least one change, to software code, that was submitted to the software repository;
parsing the difference file to determine one or more files, associated with the software code, affected by the at least one change and to determine content associated with the at least one change,
wherein parsing the difference file to determine the one or more files comprises determining a change in one or more filenames identified in the software code based on association with a file extension;

applying one or more rules, from a rule dictionary, based on comparing one or more identifiers, associated with the one or more files, with one or more identifiers included in the one or more rules and based on comparing the content, associated with the at least one change, with content included in the one or more rules, wherein at least two different rule dictionaries have rules including different identifiers or different content;
generating one or more software review checklist items based on applying the one or more rules;
outputting the one or more software review checklist items for display;
receiving, based on input from a user, confirmation of the at least one change; and
committing the at least one change to the software repository based on the confirmation.

2. The computer-implemented method of claim 1 , wherein comparing the one or more identifiers, associated with the one or more files, with the one or more identifiers included in the one or more rules comprises:
comparing one or more file extensions, associated with the one or more files, with one or more file extensions included in the one or more rules; or
comparing one or more file names, associated with the one or more files, with one or more file names included in the one or more rules.

3. The computer-implemented method of claim 1 , wherein comparing the content, associated with the at least one change, with the content included in the one or more rules comprises:
comparing one or more function names, associated with the at least one change, with one or more function names included in the one or more rules;
comparing a quantity of lines, associated with the at least one change, with one or more line thresholds indicated by the one or more rules; or
comparing a quantity of files, associated with the at least one change, with one or more file thresholds indicated by the one or more rules.

4. The computer-implemented method of claim 1 , wherein comparing the one or more identifiers, associated with the one or more files, with the one or more identifiers included in the one or more rules comprises:
comparing one or more file identifiers, associated with one or more new files associated with the at least one change, with one or more new file identifiers included in the one or more rules; or
comparing one or more file identifiers, associated with one or more removed files associated with the at least one change, with one or more removed file identifiers included in the one or more rules.

5. The computer-implemented method of claim 1 , further comprising:
extracting, from the difference file, at least one identifier for a team associated with the software code or for a project associated with the software code; and
selecting the rule dictionary based on the at least one identifier.

6. The computer-implemented method of claim 1 , wherein receiving the confirmation comprises:
receiving the confirmation based on one or more interactions with a graphical user interface (GUI) that provides the one or more software review checklist items for display.

7. The computer-implemented method of claim 1 , wherein generating the one or more software review checklist items comprises:
adding at least one item to a preconfigured checklist; or
removing at least one item from the preconfigured checklist.

8. The computer-implemented method of claim 7 , further comprising:
retrieving the preconfigured checklist from at least one memory including a plurality of preconfigured checklists.

9. A system for rule-based review of software code changes, the system comprising:
one or more memories; and
one or more processors, communicatively coupled to the one or more memories, configured to:
receive, from a software repository, a difference file indicating at least one change, to software code, that was submitted to the software repository;
parse the difference file to determine one or more files, associated with the software code, affected by the at least one change,
wherein parsing the difference file to determine the one or more files comprises determining a change in one or more filenames identified in the software code based on association with a file extension;

select a rule dictionary that identifies one or more rules associated with software code changes;
apply the one or more rules to generate one or more software review checklist items, wherein at least two different rule dictionaries cause generation of different software review checklist items;
output a graphical user interface (GUI) that provides the one or more software review checklist items for display;
receive, based on input from a user and using the GUI, confirmation of the at least one change; and
commit the at least one change to the software repository based on the confirmation of the at least one change.

10. The system of claim 9 , wherein the one or more processors are further configured to:
determine at least one identifier for a team associated with the software code or for a project associated with the software code; and
wherein the one or more processors, when selecting the rule dictionary, are configured to select the rule dictionary based on the at least one identifier.

11. The system of claim 10 , wherein the one or more processors, when receiving the difference file, are configured to:
receive a pull request from the software repository, wherein the pull request includes the difference file; and
wherein the at least one identifier is determined from the pull request.

12. The system of claim 9 , wherein the one or more processors, when receiving the confirmation of the at least one change, are configured to receive confirmation that the one or more software review checklist items have been completed; and
wherein the one or more processors, when committing the at least one change to the software repository, are configured to commit the at least one change to the software repository based on the confirmation that the one or more software review checklist items have been completed.

13. The system of claim 9 , wherein the one or more processors are further configured to:
generate an error message when the input from the user does not confirm the one or more software review checklist items.

14. The system of claim 9 , wherein the one or more processors, when receiving the difference file, are configured to:
receive the difference file using at least one an application programming interface (API) call, wherein the API call is triggered by the software repository using a webhook.

15. The system of claim 9 , wherein the one or more processors are further configured to:
determine content associated with the at least one change; and
wherein the one or more processors, when applying the one or more rules, are configured to apply the one or more rules based on comparing one or more identifiers, associated with the one or more files, with one or more identifiers included in the one or more rules and b

Assignees

• Capital One Services Llc

Inventors

• Kay Tallulah
• Simon Benjamin
• Kim Christina
• Khan Naveed
• Ibrahim Ahmad
• Lavallee Jean-Etienne
• Swain George
• Almanzar Steven
• Kim Andrew
• Leone Dominic

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/73

  Program documentation · CPC title

• G06F8/20

  Software design · CPC title

• G06F9/451

  Execution arrangements for user interfaces · CPC title