wa:deploy-promote

To safely merge a dev branch to main, you can use a CI-gated promotion workflow that blocks branch promotion when CI validation is failing on the integration branch. This ensures broken releases are prevented by confirming CI health before updating production.

The best merge strategy for promoting dev to production depends on your history requirements. A fast-forward only strategy is default for clean histories, but you can select a merge commit strategy when appropriate to preserve context during branch promotion.

To verify branches are in sync after branch promotion, use a multi-stage workflow that performs git merge primitives, pushes main, and confirms both dev and main are synchronized afterward. This post-update verification ensures the lifecycle integration succeeded.

Yes, you can use fast-forward only merges for automated E2E dev-to-main updates. This release workflow supports CI/CD-driven environments by enforcing branch divergence validation and utilizing fast-forward only by default to safely update the production branch.

Branch promotion fails when CI validation is failing because the workflow enforces CI health checks before merging. This prevents broken releases by blocking the dev integration branch from updating the main production branch until all CI checks pass.

You need branch divergence validation before merging dev to production when following a controlled dev-to-main lifecycle. It ensures the candidate branch has passed CI and checks branch readiness before applying the correct git merge primitive to update main.