{"version":"2.1.223","anchor":"fetch-output-branch-parsing-requires-hex-ranges","canonical_anchor":"fetch-output-branch-parsing-requires-hex-ranges","heading":"Fetch-output branch parsing requires hex ranges","tier":"internal","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/fetch-output-branch-parsing-requires-hex-ranges","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Fetch-output branch parsing requires hex ranges\n\nGit fetch output is parsed more strictly, so unrelated lines aren't mistaken for updated branches.\n\n**What**\n\nParsing of `git fetch` output is stricter about what counts as an updated ref, reducing false matches on unrelated fetch lines.\n\n**Details**\n\n- The old..new range must now consist of hex characters rather than any non-whitespace token.\n- The `[new branch]` alternative is unchanged.\n\n**Evidence**\n\n`[0-9a-f]+\\.\\.+[0-9a-f]+`\n\n- Area: Git Integration\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}