safe-push

To safely rebase and run tests before a git push, you need a workflow that fetches remote changes, applies a conditional rebase, runs automated test verifications, and pauses for manual review if drift is detected.

Your git push fails when the remote branch has advanced because local commits diverge from the remote history. A safe push workflow resolves this by fetching updates and conditionally rebasing your local commits before pushing.

The best way to automate a git fetch, rebase, and testing workflow is using a safe push helper that coordinates these steps sequentially, requires a clean worktree, and supports specifying custom test commands.

Yes, you can use a safe push workflow for non-default branches with custom test commands. This flexible approach supports optional test execution and allows specifying target branches during the push operation.

No, safe push does not auto-resolve git rebase conflicts. It requires a clean worktree and mandates a manual audit to resolve any detected drift, ensuring you review changes instead of automatically committing potentially broken code.

You need to rerun tests after rebasing local git commits when the remote branch has advanced and a rebase is applied. This ensures the newly integrated code still passes verifications before the final push.