# Push to a remote group mishandles --force-with-lease

_A bare --force-with-lease was never forwarded to each remote in the group, and an expect-absent lease could overwrite a remote branch._

Section: Bugs. Edition of 2026-11-05. Written by an AI editor from the thread "[PATCH] push: fix --force-with-lease forwarding in push_multiple()" (3 messages): https://gitlist.dev/t/66763

Cipriani says 8ea8281665 (push: support pushing to a remote group, 2026-05-03) mishandled --force-with-lease.

In the first bug, a bare --force-with-lease is never forwarded to the remote group. The bare option sets cas.use_tracking_for_rest without adding a cas entry, and only cas entries are forwarded. Non-fast-forward pushes are therefore always rejected.

In the second, --force-with-lease=<ref>: means the ref is expected to be absent on the remote. It 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.

The patch credits Patrick Peroša with the report. He sent a revised version of the commit message, and Kristoffer Haugsbakk replied. The excerpts do not show the substance of that reply.
