Salesforce Trunk-based Development [exclusive] -

| 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 . |

Salesforce Trunk-Based Development: The Ultimate Guide Trunk-based development (TBD) is a version control strategy where developers merge small, frequent updates into a single central branch, known as the "trunk" or "main" branch. While traditional software engineering has long favored this model for high-velocity teams, it is now becoming the gold standard for . salesforce trunk-based development

Move from GitFlow to 3-day feature branches, then compress to 24 hours, then adopt TBD fully. Your CI pipeline and metadata hygiene will thank you. | Pitfall | Solution | |---------|----------| | "We

Without feature toggles, TBD forces incomplete features into production. Use these patterns: full regression (slow)