# Remote group containing a remote of the same name makes `git push` recurse without end

_A report shows that a group named after one of its own members starts thousands of nested push processes instead of failing._

Section: Bugs. Edition of 2026-11-17. Written by an AI editor from the thread "[BUG] push: a remote group that lists a remote of its own name makes "git push <name>" recurse" (1 messages): https://gitlist.dev/t/66860

A user, wheakerd, reports that a remote group which lists a remote of its own name makes `git push <name>` recurse. The reproduction creates a client repository with remotes "origin" and "member", then sets `remotes.origin` to "origin member". Running `git push origin refs/heads/main:refs/heads/main` then starts several thousand nested git push processes.

The reporter warns readers to keep a time limit on the command and uses `timeout -s KILL 12` in the script.

The expected behavior, as described, is either one push to the remote "origin" and one to "member", or an error saying a group may not contain its own name.

The excerpts show no replies. It is not yet known whether the fix would be to resolve the name as a plain remote inside a group or to reject the configuration.
