Choose safety settings

Start with safe defaults, enable extra actions deliberately, and protect production repositories.

Begin with the defaults

push& (Pushand) uses your installed Git and existing access. In Settings, the Safety section lets you choose global defaults or an override for one repository. A repository override applies to all its worktrees.

The starting settings allow pushing to an existing tracked remote branch and pulling by fast-forward. Publishing a new branch asks each time. Pushing tags, pulling with rebase, rewriting remote history, deleting remote branches and discarding worktree changes start off.

Fast-forward pull refuses diverged or uncommitted work. It also refuses to overwrite ignored files. An ordinary push refuses a branch that is behind or diverged.

Enable extra actions deliberately

Publishing creates a new remote branch. Keep Ask each time unless you want publishing to be allowed without that question for the repository.

Other optional actions appear when enabled and applicable. Before enabling one, consider its effect:

  • Pushing a tag shares that tag on the remote.
  • Pulling with rebase can rearrange your local commits.
  • Rewriting remote history replaces the tracked remote branch with your local history. It requires the repository name and refuses conflicting remote changes detected during the action.
  • Deleting a remote branch removes it from the remote; the local branch remains on your Mac. It also requires the repository name.

Turning an option off later cannot undo an action you already confirmed.

Mark production repositories

Use Production repositories in Settings to mark repositories that need extra care. Production status covers every worktree of the repository.

For every action on a production repository, type the repository name to confirm. Automatic cleanup skips production repositories. Read the branch and action as well as the name before confirming.

Review before discarding work

Merged and pushed cleanup is suggested for Pro, Unlimited, Beta and trial users. Automatic cleanup is optional and only handles clean worktrees.

Removing a worktree with uncommitted or ignored files needs a separate opt-in setting, a displayed file list and typed-name confirmation. Those files can be lost. Read Review cleanup before enabling it.

Treat errors as a reason to review

If an action is refused, read its message and check the branch state before trying again. You may need to finish an operation in Git, restore folder access, or refresh after the remote changes. Leave optional actions off unless you intend their consequences.

For the approved explanation of app connections and data handling, read the privacy policy.

Back to the Guide · Need a hand? Contact us