Improvements to source control on Workflows are now generally available on Self-hosted Retool 3.200.0-edge and in the upcoming stable release. The following features are now supported for all users on Enterprise plans:

Retool made several improvements to the usage of Source Control with Retool Workflows. The following features are now supported on Enterprise plans:

• Branched changes. You can now make changes to workflows using branches. Previously, all Source Control changes on workflows were branchless.
• Multi-element branching. You can make edits to workflows on the same branch as edits to apps, modules, and Query Library queries.
• Collaborative branches. Multiple users can commit changes and merge pull requests on collaborative branches.

If your organization uses Source Control, Retool sometimes creates an automatic commit, called a catch-up commit, which keeps your branches up to date. If you want to ensure that developers in your organization retain complete control of changes within their feature branches, you can now disable catch-up commits using the following steps:

1. Navigate to Settings > Source Control and click the Edit Settings button on the top right.
2. Toggle on the Disable auto catch up commits setting.

To avoid issues with catch-up commits and other merge control mechanisms, refer to Retool's Merge conflict prevention strategies.

You can now test deployments when using Source Control, preventing changes that leave your Retool instance in a broken state. Retool added the Test source control changes endpoint to the Retool API, which enables you to test whether implementing a change will result in deployment issues.

You can also incorporate this check into your continuous integration process if desired.

Enterprise users can now protect organization-level themes using Source Control. This enables you to safely replicate organization-level theme configurations across multiple instances of Retool. You can use protected themes with any of Retool's supported source control management (SCM) providers.

Retool will deprecate the use of YAML for protected apps, queries, and resources in Source Control. Support will be removed in the Q2 2025 stable release of Self-hosted Retool.

Self-hosted organizations still using YAML serialization of these elements in Source Control must migrate to Toolscript prior to upgrading.

Organizations with self-hosted deployments must manually deploy latest changes when upgrading to self-hosted Retool 3.52 or later to ensure that recent updates to Source Control are applied.

You can now enable collaborators on Source Control branches. Source Control branches are private by default and only allow changes by the owner. On collaborative branches, multiple users can commit changes and submit pull requests to protected elements.