{"version":"2.1.140","anchor":"user-identity-added-to-branch-pattern-context","canonical_anchor":"user-identity-added-to-branch-pattern-context","heading":"User Identity Added to Branch Pattern Context","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140\/e\/user-identity-added-to-branch-pattern-context","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140","markdown":"### User Identity Added to Branch Pattern Context\n\n**What**\n\nClaude now receives the current user's identity (derived from `GITHUB_ACTOR`, `USER`, or `USERNAME`, or the email username) to correctly resolve the `$USER\/...` personal-branch pattern in rules.\n\n**Details**\n\n- A new context line is injected: `**User identity**: \\`<name>\\`. The \\`$USER\/...\\` pattern in the rules above resolves to \\`<name>\/...\\`. Branches whose first path segment is a different person's name (\\`<other-user>\/...\\`) are NOT this user's personal branches.`\n- This prevents Claude from treating sibling developers' branches as the user's own.\n\n**Evidence**\n\n`rm_()` function (search for `\"Branches whose first path segment is a different person's name\"`)"}