[Feature] - Push, Pull, Clone - Git like architecture for scripting

Feature Requests Studio Features
, ,
1

Issue :information_source:

As a developer who has been active on the Roblox platform for 8 years and coding for the past 3, it is currently too difficult to collaboratively write and review code with a team. Unless a team goes through the friction of migrating their workflow entirely off-platform using third-party tools like Rojo, managing multi-developer scripting pipelines within Roblox Studio is incredibly frustrating and error-prone.

Even though Roblox offers two primary modes of team scripting Live Script Editting and Drafts, they introduce massive bottlenecks that derail professional development structures.

1. Problems of Live Editting

  • Lack of Code Isolation: Live editing forces multiple developers into a single script simultaneously. If Developer A is mid-thought and typing half-broken code, it actively disrupts Developer B who is working on an entirely separate function inside the same file.
  • Accidental Overwrites: Without an isolated environment to test changes safely before they go “live,” developers frequently step on each other’s toes, inadvertently breaking the game state for the rest of the team during active sessions.

2. Problems with the Drafts System

  • Lack of Gated Quality Control: Currently, any developer with script editing permissions can blindly commit their draft to the server. There is no structural hierarchy or code review process, allowing broken or unvetted logic to pollute the main file.

Proposed Solution: Git-like architecture :information_source:

We need an on-platform, highly visual git-inspired workflow for modern, team-based Roblox development. This includes distributed code ownership, visual version timelines, and explicit code-review roles.

1. Visual Commit Timeline (Right-Click > “View Timeline”)

Instead of reading through text logs, version control should be entirely visual.

  • Right-clicking a script and selecting “View Timeline” should open a modern, horizontal graph spanning across the screen.
  • A central line represents the Main production branch, with colored nodes branching outward and returning to the main line, visually mapping exactly who branched, who pushed, and when changes were merged.

2. Micro-Branching and Script “Ownership”

  • Isolated Cloning: Developers can “Clone” any script to create their own isolated branch.
  • Live Observation without Co-Editing Interference: When Developer A clones a script, an “Ownership” tag is bound to that branch. Developer B can view Developer A’s branch and watch their changes update live in real-time, but they cannot directly co-edit it. If Developer B wants to build off that logic, they must clone their own copy or explicitly copy/paste elements out of it.

3. The “Merge Master” & Code Gatekeeping

To maintain strict technical structures within professional studios, team hierarchies need to be natively supported via Group Permissions:

  • “Can Push to Main Branch” Toggle: Group owners should have a permission toggle to designate senior developers or Tech Leads as Merge Masters.
  • Pull Request Workflow: Junior or mid-level developers can push final commits from their cloned branches, but those commits do not automatically inject into the live game.
  • Granular Merging: The Merge Master is notified of incoming commits, allowing them to open a visual diff viewer to pick-and-choose specific functions to merge into the main branch, or choose to merge the branch blindly after a thorough code review.

Why Roblox Should Implement This :information_source:

The current toolchain forces professional teams to choose between the chaotic nature of Live Editing, the frustratingly rigid conflicts of Drafts, or abandoning Roblox Studio’s built-in script editor entirely for external IDEs like VS Code integrated with Rojo and maintaining clean repositories at GitHub. Too much set-up requried.

By implementing an intuitive, visual, and role-gated branching architecture directly inside Studio, Roblox will drastically lower the barrier to entry for professional game development, reduce team workflow friction, and elevate the standard of collaborative engineering on the platform.

2 Likes