safe-push

To safely push commits to a protected branch, use the safe-push workflow to enforce automated validation, dry-run capability, and CI tests before merging changes. It verifies tests and CI results before allowing the merge.

The best way to validate a feature push to master is initiating a Safe Push in dry-run mode to validate CI checks before merging changes to a protected branch. This verifies tests and CI results beforehand.

Yes, you can execute an emergency push to a protected branch when builds fail. The safe-push workflow supports emergency push scenarios to revert or fix critical issues even when tests or builds fail.

Yes, you need the safePush.cmd CLI script and configuration to automate the safe push workflow. It requires this script to verify tests and CI results before merging changes to the protected branch.

To consolidate feature commits before pushing to a protected branch, the safe-push workflow provides optional autosquash options for commits before pushing. This ensures a clean commit history during automated validation.

Safe-push tracks CI progress during the merge validation process by integrating with Patronus CI and providing monitoring links. This allows you to track progress while it verifies tests and CI results before merging.