Salesforce Trunk-based Development =link= Jun 2026

By moving away from long-lived feature branches that often lead to "merge hell," Salesforce teams can achieve faster release cycles and higher environment stability. 1. Why Trunk-Based Development for Salesforce?

Trunk-Based Development (TBD) is a source-control workflow where developers collaborate on code in a single branch (the "trunk," usually named main or master ). It is widely considered the gold standard for Continuous Integration and Delivery (CI/CD) because it minimizes merge conflicts, reduces complexity, and accelerates release cycles.

By following these guidelines and best practices, you can successfully implement trunk-based development in your Salesforce environment, improving collaboration, reducing integration issues, and speeding time-to-market. salesforce trunk-based development

Implementing Trunk-Based Development in Salesforce Trunk-Based Development (TBD) is a version control strategy where developers merge small, frequent updates to a single central branch—the "trunk." In the context of Salesforce, this approach contrasts with traditional "feature branching" and is a cornerstone of modern

Once approved and CI passes:

| Pitfall | Solution | |---------|----------| | "We need long branches because profiles are hard to merge" | Move profile overrides to Permission Sets or use sfdx-git-delta . | | "Our scratch orgs take 30 minutes to create" | Use pre-configured scratch orgs (snapshots) or increase CI parallelism. | | "We can't test all Apex in 10 minutes" | Split tests: critical path (fast) vs. full regression (slow). | | "Our UAT requires a stable environment" | Deploy main to a dedicated UAT sandbox daily, not per commit. | | "We have managed packages that require versioning" | Use CI to auto-increment package version on each merge to main . |

Problem: Deleting metadata must be coordinated across all devs. Solution: By moving away from long-lived feature branches that

Trunk-based development is a version control management strategy that involves working on a single, main branch (the "trunk") and frequently merging changes into it. This approach encourages collaboration, reduces integration problems, and makes it easier to manage releases.

on: pull_request: branches: [ main ]

Without feature toggles, TBD forces incomplete features into production. Use these patterns: