{"version":"2.1.229","anchor":"updating-an-existing-pr-no-longer-passes-a-pr-number","canonical_anchor":"updating-an-existing-pr-no-longer-passes-a-pr-number","heading":"Updating an existing PR no longer passes a PR number","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/updating-an-existing-pr-no-longer-passes-a-pr-number","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Updating an existing PR no longer passes a PR number\n\nUpdating an existing PR now relies on your branch instead of passing a PR number.\n\n**What**\n\nThe commit and PR prompt now tells Claude to update an existing PR with `--title` and `--body` and no PR number or URL, since `gh` already resolves the current branch's PR.\n\n**Evidence**\n\n`(gh resolves the current branch's PR when no selector is given)`\n\n- Area: Slash Commands\n- Names: `--title`, `--body`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}