VBS Branching Best Practice for Multi-User Teams and Separate DEV/TEST/PROD Deployments

Hi all,

we are using Visual Builder Studio (VBS) in a project with multiple developers/admin users working in parallel and deploying changes across DEV, TEST, and PROD environments.

Current situation

• Each developer works in their own workspace and branch
• Changes are delivered using Publish, which merges everything into main
• Our deployment pipelines for different environments use main as the source branch

Problem in a multi-user setup

With several people publishing changes, main quickly contains a mix of unrelated features and fixes.

When we run a deployment to DEV or PROD, we cannot select only specific changes all updates already merged into main are deployed togethe