You'll notice
Git push permission rules can now include both origin and a custom pushDefault remote at once
What
When Claude Code figures out which git remotes to grant push permission for (so it can suggest a rule like git push origin *), it now returns multiple candidate remotes instead of picking just one. It includes origin when present, plus whatever remote is configured as remote.pushDefault, as long as that name fits an expected naming pattern.
Why
Repos that push to both origin and a separate configured push remote (like a fork or an upstream) now get permission rules covering both, instead of Claude Code having to choose only one and potentially still prompting for the other.
Names in the bundleremote.pushDefault