{"version":"2.1.273","anchor":"pr-tracking-regex-replaced-with-a-streaming-scan-supporting","canonical_anchor":"pr-tracking-regex-replaced-with-a-streaming-scan-supporting","heading":"PR\/change tracking now extracts and reports the source branch","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/pr-tracking-regex-replaced-with-a-streaming-scan-supporting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### PR\/change tracking now extracts and reports the source branch\n\nClaude Code now detects the head\/source branch of gh\/glab PR creations and reports it as the branch a new change was opened from\n\n**What**\n\n- The code that scans bash command output for `gh pr create` \/ `glab mr create` invocations to link a session to a pull request was rewritten to also extract the target branch, from a `--head`\/`-H` (gh) or `--source-branch`\/`-s` (glab) flag, and validate it as a safe git ref before using it.\n\n- The `branch` field reported to a host for VCS changes is now documented to carry this branch information more broadly: not just for providers without their own head-branch concept (like Gerrit), but for any provider when the change's kind is `created`, using the branch the create was opened from.\n\n**Why** This lets a host display the branch a newly created pull request or change came from immediately, before the host's own lookup against the forge (like GitHub or GitLab) responds.\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}