IP Library Granted Patent US 12,307,243
Granted Patent B2
US 12,307,243 · App. 17/580,499 · Granted May 20, 2025

Code management cross-support and synchronization

Inventors: Patrick Calahan (San Francisco, CA); Vishrut Dixit (Chicago, IL); Jonathan Thomas Hays (Grass Valley, CA)
Assignee: Salesforce, Inc.
G06F8/71
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,307,243
App. No.
17/580,499
Granted
May 20, 2025
Kind
B2
Abstract

A method for managing code development includes receiving, from a workspace, a request for a primary set of code in a first repository, providing, in response to the request, the primary set of code to the workspace with support for code management for the primary set of code from a first code management system, and providing, in response to the request, a secondary set of code to the workspace with support for code management for the supporting set of code from a second code management system.

Claims (44)

1. A method for managing code development, the method comprising:

receiving, from a workspace, a request for a primary set of code in a first repository;

providing, in response to the request, the primary set of code to the workspace with support for code management for the primary set of code from a first code management system, wherein the primary set of code has been migrated from a second code management system to the first code management system based on an enlistment that identifies source code files to be migrated to the first code management system;

providing, in response to the request and based on access detection of the primary set of code, a secondary set of code to the workspace with support for code management for the secondary set of code from the second code management system;

submitting a first set of changes to the primary set of code to the first code management system;

testing the first set of changes for issues; and

converting the first set of changes to a change list compatible with the second code management system.

2. The method of claim 1 , further comprising:

retrieving the primary set of code from the first repository; and

identifying the secondary set of code and a location of the secondary set of code, where the secondary set of code supports execution of the primary set of code.

3. The method of claim 1 , further comprising:

submitting the change list to the second code management system.

4. The method of claim 3 , further comprising:

merging changes of the primary set of code from the first code management system with a copy of the primary set of code at the second code management system.

5. A non-transitory machine-readable storage medium that provides instructions that, if executed by a set of one or more processors, are configurable to cause said set of one or more processors to perform operations comprising:

receiving, from a workspace, a request for a primary set of code in a first repository;

providing, in response to the request, the primary set of code to the workspace with support for code management for the primary set of code from a first code management system, wherein the primary set of code has been migrated from a second code management system to the first code management system based on an enlistment that identifies source code files to be migrated to the first code management system;

providing, in response to the request, a secondary set of code to the workspace with support for code management for the secondary set of code from the second code management system;

submitting a first set of changes to the primary set of code to the first code management system;

testing the first set of changes for issues; and

converting the first set of changes to a change list compatible with the second code management system.

6. The non-transitory machine-readable storage medium of claim 5 , providing further instructions to cause the set of one or more processors to perform further operations comprising:

retrieving the primary set of code from the first repository; and

identifying the secondary set of code and a location of the secondary set of code, where the secondary set of code supports execution of the primary set of code.

7. The non-transitory machine-readable storage medium of claim 5 , providing further instructions to cause the set of one or more processors to perform further operations comprising:

submitting the change list to the second code management system.

8. The non-transitory machine-readable storage medium of claim 7 , providing further instructions to cause the set of one or more processors to perform further operations comprising:

merging changes of the primary set of code from the first code management system with a copy of the primary set of code at the second code management system.

9. An apparatus comprising:

a non-transitory machine-readable storage medium that stores software; and

a set of one or more processors, coupled to the non-transitory machine-readable storage medium, to execute the software that implements a code management service and that is configurable to:

receive, from a workspace, a request for a primary set of code in a first repository,

provide, in response to the request, the primary set of code to the workspace with support for code management for the primary set of code from a first code management system, wherein the primary set of code has been migrated from a second code management system to the first code management system based on an enlistment that identifies source code files to be migrated to the first code management system; and

provide, in response to the request and based on access detection of the primary set of code, a secondary set of code to the workspace with support for code management for the secondary set of code from the second code management system;

submitting a first set of changes to the primary set of code to the first code management system;

testing the first set of changes for issues; and

converting the first set of changes to a change list compatible with the second code management system.

10. The apparatus of claim 9 , wherein the set of one or more processors is further configurable to:

retrieve the primary set of code from the first repository; and

identify the secondary set of code and a location of the secondary set of code, where the secondary set of code supports execution of the primary set of code.

11. The apparatus of claim 9 , wherein the set of one or more processors is further configurable to:

submit the change list to the second code management system.

12. The apparatus of claim 11 , wherein the set of one or more processors is further configurable to:

merge changes of the primary set of code from the first code management system with a copy of the primary set of code at the second code management system.

Assignments (2)
CHANGE OF NAME Recorded Feb 17, 2023
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 062794/0656 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 20, 2022
From: CALAHAN, PATRICK; DIXIT, VISHRUT; HAYS, JONATHAN THOMAS
To: SALESFORCE.COM, INC.
Reel/Frame 058716/0397 →