# US 2026/0230507 A1 · Deploying a branch of a main codebase based on security policy compliance since creation of the branch

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0230507 A1
- Document ID: US20260230507A1
- Status: Published application
- Kind: A1
- Application number: 19/045,506
- Filed: 2025-02-04
- Published: 2026-08-06
- Earliest claimed: 2025-02-04
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Jose Luis MENDOZA AZANZA; Alexander Geoffrey HOWELLS; Oleg SURMACHEV; Vishwa Shobhit SAHAY; Haixia LING; Mikhail DEMYANYUK; Erica Miyisha TURNER-SUMIYOSHI; Haris Farhan MOHAMMAD
- Web page: https://patentgrep.com/patent/US20260230507A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 21/51: at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F 8/60: Software deployment
- G06F 2221/033: Test or assess software
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are described herein that are capable of deploying a branch of a main codebase based on compliance of the branch with a security policy since creation of the branch(es). A first branch of a main codebase is stored in a designated store and a second branch of the main codebase is not stored in the designated store as a result of the first branch complying with a security policy throughout a first time period since creation of the first branch and the second branch failing to comply with the security policy during a second time period since creation of the second branch. As a result of the first branch being stored in the designated store and complying with the security policy throughout the first time period, the first branch is converted into a deployable code branch, and the deployable code branch is deployed.

## Claims

### Claim 1

A system comprising:
a processor system; and
a memory that stores computer-executable instructions that are executable by the processor system to at least:
as a result of a first branch of a main codebase undergoing an official build, store the first branch in a designated store;
as a result of verifying that a second branch of the main codebase has complied with a security policy since creation of the second branch, store the second branch in the designated store;
determine that a deployment criterion is satisfied by verifying that the first branch and the second branch are stored in the designated store and that the first branch and the second branch have complied with the security policy since being stored in the designated store;
as a result of the deployment criterion being satisfied, generate a first deployable code branch and a second deployable code branch by building the first branch and the second branch, respectively; and
as a result of a request to deploy a build of the main codebase being received, deploy the first deployable code branch and the second deployable code branch.

### Claim 2 (depends on 1)

The system of claim 1, wherein the computer-executable instructions are executable by the processor system to at least:
sign the first deployable code branch and the second deployable code branch with a production certificate; and
as the result of the request to deploy the build of the main codebase being received and the first deployable code branch and the second deployable code branch being signed with the production certificate, deploy the first deployable code branch and the second deployable code branch.

### Claim 3 (depends on 1)

The system of claim 1, wherein the security policy specifies that merging an arbitrary change that is comprised in an arbitrary branch of the main codebase into the main codebase is conditioned on satisfaction of a prerequisite, the prerequisite comprising creation of a pull request, which requests merging the arbitrary change into the main codebase, and further comprising approval of the pull request;
wherein the computer-executable instructions are executable by the processor system further to at least:
commit a change in a specified branch of the main codebase, which comprises merging the change into the main codebase by performing the following operations in satisfaction of the prerequisite:
create a first pull request, which requests a merge of the change into the main codebase; and
receive approval of the first pull request as a result of the change complying with the security policy; and
wherein the specified branch is the first branch or the second branch.

### Claim 4 (depends on 3)

The system of claim 3, wherein the computer-executable instructions are executable by the processor system to at least:
store the second branch of the main codebase in the designated store as a result of the first pull request being created and the approval of the first pull request being received.

### Claim 5 (depends on 3)

The system of claim 3, wherein the computer-executable instructions are executable by the processor system to determine that the deployment criterion is satisfied by performing the following operations:
determine that the first pull request is created during a time period that temporally follows storage of the specified branch in the designated store; and
determine that the approval of the first pull request is received; and
wherein the computer-executable instructions are executable by the processor system to generate the first deployable code branch and the second deployable code branch by building the specified branch as a result of the first pull request being created during the time period that temporally follows the storage of the specified branch in the designated store and the approval of the first pull request being received.

### Claim 6 (depends on 3)

The system of claim 3, wherein the computer-executable instructions are executable by the processor system to at least:
receive the approval of the first pull request as a result of the change being reviewed by a number of reviewers that is greater than or equal to a threshold number, wherein the threshold number is greater than or equal to two.

### Claim 7 (depends on 3)

The system of claim 3, wherein the computer-executable instructions are executable by the processor system to at least:
receive the approval of the first pull request as a result of the change being reviewed by a designated reviewer that is identified by the security policy.

### Claim 8 (depends on 3)

The system of claim 3, wherein the computer-executable instructions are executable by the processor system to at least:
receive the approval of the first pull request as a result of the first pull request being created at a designated computing system, which is identified by the security policy.

### Claim 9 (depends on 3)

The system of claim 3, wherein the computer-executable instructions are executable by the processor system to at least:
receive the approval of the first pull request further as a result of the security policy remaining at least one of unchanged since the creation of the second branch of the main codebase or enforced since the creation of the second branch of the main codebase.

### Claim 10

A method implemented by a computing system, the method comprising:
storing a first branch of a main codebase in a designated store, instead of storing a second branch of the main codebase in the designated store, as a result of the first branch continuously complying with a security policy since creation of the first branch and the second branch failing to continuously comply with the security policy since creation of the second branch;
as a result of the first branch of the main codebase being stored in the designated store and the first branch continuing to comply with the security policy since the first branch was stored in the designated store, converting the first branch into a deployable code branch by building the first branch; and
in response to a request to deploy a build of the main codebase, deploying the deployable code branch.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
signing the deployable code branch of the main codebase with a production certificate; and
wherein deploying the deployable code branch comprises:
in response to the request to deploy the build of the main codebase, deploying the deployable code branch of the main codebase as a result of the deployable code branch being signed with the production certificate.

### Claim 12 (depends on 10)

The method of claim 10, wherein the security policy specifies that merging an arbitrary change that is comprised in an arbitrary branch of the main codebase into the main codebase is conditioned on satisfaction of a prerequisite, the prerequisite comprising creation of a pull request, which requests merging the arbitrary change into the main codebase, and further comprising approval of the pull request; and
wherein the method further comprises:
committing a change that is comprised in the first branch of the main codebase, the committing comprising merging the change into the main codebase by performing the following operations in satisfaction of the prerequisite:
creating a first pull request, which requests a merge of the change into the main codebase; and
receiving approval of the first pull request as a result of the change complying with the security policy.

### Claim 13 (depends on 12)

The method of claim 12, wherein storing the first branch in the designated store comprises:
storing the first branch of the main codebase in the designated store as a result of the first pull request being created and the approval of the first pull request being received.

### Claim 14 (depends on 12)

The method of claim 12, wherein converting the first branch into the deployable code branch comprises:
converting the first branch of the main codebase into the deployable code branch as a result of the first pull request being created during a time period that temporally follows storage of the first branch in the designated store and the approval of the first pull request being received.

### Claim 15 (depends on 12)

The method of claim 12, wherein the approval of the first pull request is received as a result of the change being reviewed by a number of reviewers that is greater than or equal to a threshold number, wherein the threshold number is greater than or equal to two.

### Claim 16 (depends on 12)

The method of claim 12, wherein the approval of the first pull request is received as a result of the change being reviewed by a designated reviewer that is identified by the security policy.

### Claim 17 (depends on 12)

The method of claim 12, wherein the approval of the first pull request is received as a result of the first pull request being created at a designated computing system, which is identified by the security policy.

### Claim 18 (depends on 12)

The method of claim 12, wherein the approval of the first pull request is received further as a result of the security policy remaining unchanged since the creation of the first branch of the main codebase.

### Claim 19 (depends on 12)

The method of claim 12, wherein the approval of the first pull request is received further as a result of the security policy remaining enforced since the creation of the first branch of the main codebase.

### Claim 20

A computer program product comprising a computer-readable storage medium having instructions recorded thereon for enabling a processor-based system to perform operations, the operations comprising:
determining, at a first time instance, whether first, second, and third branches of a main codebase comply with a security policy throughout respective first, second, and third time periods that begin at creation of the first, second, and third branches and that end at the first time instance;
storing the first and second branches of the main codebase in a designated store, instead of storing the third branch in the designated store, as a result of the first and second branches complying with the security policy throughout the respective first and second time periods and the third branch failing to comply with the security policy during the respective third time period;
converting, at a second time instance, the first branch into a deployable code branch by building the first branch, instead of building the second branch, as a result of the first branch being stored in the designated store and the first branch complying with the security policy throughout a fourth time period and the second branch failing to comply with the security policy during the fourth time period, wherein the fourth time period begins at the first time instance and ends at the second time instance; and
as a result of a request to deploy a build of the main codebase being received, deploying the deployable code branch.
