{"version":"2.1.236","anchor":"git-command-matching-no-longer-lets-an-option-name-contain","canonical_anchor":"git-command-matching-no-longer-lets-an-option-name-contain","heading":"Git command matching no longer lets an option name contain '='","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/git-command-matching-no-longer-lets-an-option-name-contain","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Git command matching no longer lets an option name contain '='\n\nGit commands with long options are classified more accurately when checking permissions.\n\n**What**\n\nThe pattern that finds the git subcommand behind global flags tightened its long-option branch, so an option name can no longer itself swallow an equals sign. This changes which `git ...` invocations are classified correctly for permissions.\n\n**Evidence**\n\n`\\\\bgit(?:\\\\s+-[cC]\\\\s+\\\\S+|\\\\s+--[^\\\\s=]+=\\\\S+)*\\\\s+`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}