# Bare --force-with-lease is ignored when pushing to a remote group; fix posted

_A regression in the new remote-group push support makes the option reject non-fast-forward pushes, and a related case could overwrite a remote branch._

Section: Bugs. Edition of 2026-11-04. Written by an AI editor from the thread "[bug] push: bare --force-with-lease ignored on remote groups" (2 messages): https://gitlist.dev/t/66755

Patrick Peroša reported that a non-fast-forward push to a remote group using bare `--force-with-lease`, with no refname or expected value, does not work. His reproduction uses two file-based bare remotes combined as a group named "both" through the remotes.both config.

Tyler Cipriani replied that he had pushed a fix as a separate thread, and noted he had meant to send it as a reply in the report thread. The patch is titled "push: fix --force-with-lease forwarding in push_multiple()".

Its commit message traces both problems to 8ea8281665 (push: support pushing to a remote group, 2026-05-03). First, bare --force-with-lease always rejects non-fast-forward pushes, because it was never forwarded: the bare option sets cas.use_tracking_for_rest without adding a cas entry, and only cas entries were forwarded.

Second, using `--force-with-lease=<ref>:`, meaning the ref is expected to be absent on the remote, could overwrite a remote branch if the ref's remote-tracking branch is up to date with the remote, which is the usual state after a fetch.

Kristoffer Haugsbakk noted only that the reporter's surname in the Reported-by trailer should be spelled Peroša. No maintainer review of the substance has appeared yet.