{"version":"2.1.206","anchor":"dynamic-git-remote-detection-for-push-permissions","canonical_anchor":"dynamic-git-remote-detection-for-push-permissions","heading":"Dynamic Git Remote Detection for Push Permissions","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.206\/e\/dynamic-git-remote-detection-for-push-permissions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.206","markdown":"### Dynamic Git Remote Detection for Push Permissions\n\n**What**\n\nPermission rules for `git push` now automatically include the repo's configured push remote, not just `origin`.\n\n**Details**\n\n- Before adding a `Bash(git push origin *)` rule, Claude now queries `git config remote.pushDefault` to find the actual configured push target.\n- If only one remote is configured, it is used regardless of name.\n- The resolved remote is added alongside `origin` in the allowed-patterns list, so both `git push origin *` and `git push {remote} *` are permitted.\n- This prevents unnecessary permission prompts for repos that push to `upstream`, a fork remote, or any non-`origin` name.\n\n**Evidence**\n\nRemote resolution (search for `\"remote.pushDefault\"`); dynamic rules (search for `\"git push -u\"` alongside `\"rwn\"`)"}