{"version":"2.1.300","anchor":"worktree-names-for-prs-use-the-pr-number-from-a-richer-parse","canonical_anchor":"worktree-names-for-prs-use-the-pr-number-from-a-richer-parse","heading":"Worktrees for pull requests still use the pr- number name after a parsing change","tier":"internal","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/worktree-names-for-prs-use-the-pr-number-from-a-richer-parse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Worktrees for pull requests still use the `pr-` number name after a parsing change\n\nClaude Code now reads more from a pull request reference, but still names its worktree `pr-` followed by the PR number\n\n**What**\n\nA worktree is a separate working copy of a git repository. When Claude Code makes one for a pull request, it now reads the pull request reference into a fuller result and takes the number from it. The worktree is still named `pr-` followed by the pull request number.\n\n**Why**\n\nThe name you see is the same. The fuller result may hold more than the number, such as the repository.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}