{"version":"2.1.319","anchor":"gh-pr-create-short-flag-patterns-added-to-a-list","canonical_anchor":"gh-pr-create-short-flag-patterns-added-to-a-list","heading":"gh pr create matching now covers -R , -F and -H placed first","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gh-pr-create-short-flag-patterns-added-to-a-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### `gh pr create` matching now covers `-R`, `-F` and `-H` placed first\n\nA list Claude Code matches `gh pr create` commands against now also catches `-R`, `-F` or `-H` right after `gh pr create`\n\n**Unclear.** It is not clear whether this list makes Claude Code allow these commands or stop them.\n\n**What**\n\n`gh pr create` opens a pull request using GitHub's command-line tool. Claude Code keeps a list of patterns for this command. The list covers three options, also called flags, which are extra words that change what a command does. Each has a short form:\n\n- `-R`, short for `--repo`\n\n- `-F`, short for `--body-file`\n\n- `-H`, short for `--head`\n\nBefore, the short-form patterns only matched when something came between `gh pr create` and the flag. They now also match when the short flag comes directly after `gh pr create`, as in `gh pr create -R owner\/repo`.\n\n**Why**\n\nA command written with the short flag first is now treated the same way as the same command with the flag further along.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}