{"version":"2.1.268","anchor":"default-safe-git-push-allowlist-now-covers-configured-remote","canonical_anchor":"default-safe-git-push-allowlist-now-covers-configured-remote","heading":"Default safe git-push allowlist now covers configured remotes, not just \"origin\"","tier":"notice","area":"Git Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/default-safe-git-push-allowlist-now-covers-configured-remote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Default safe git-push allowlist now covers configured remotes, not just \"origin\"\n\nAuto-approved git push rules now cover your configured push remote, not just \"origin\"\n\n**What**\n\nThe default list of `git push` commands Claude Code will run without asking permission is now built by checking your actual git remotes: it keeps `origin` if present, and adds `remote.pushDefault` if it names a single valid remote. It then expands this into allow-list entries for `git push <remote> *` and `git push -u <remote> *`, plus a certified form, for every default allow-list used across the app.\n\n**Why**\n\nRepositories that push to a remote other than `origin` (such as `upstream` or a fork remote) will no longer trigger unnecessary permission prompts for ordinary pushes to their normal configured remote.\n\n- Area: Git Permissions\n- Names: `remote.pushDefault`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}