{"version":"2.1.319","anchor":"runner-checkout-hook-gets-unique-folder-names-per-session","canonical_anchor":"runner-checkout-hook-gets-unique-folder-names-per-session","heading":"Checked-out repositories get numbered folder names when names clash","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/runner-checkout-hook-gets-unique-folder-names-per-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Checked-out repositories get numbered folder names when names clash\n\nWith a checkout hook, a repository whose folder name clashes with one already used in the session, ignoring case, now gets a -2 or -3 suffix\n\n**What**\n\nA checkout hook is a step that fetches a repository into a folder for Claude Code's runner to work in. Before, the folder was always named after the repository's short name (its slug). Now, when a checkout hook is in use and that folder name is already taken in the same session, Claude Code adds a number to the end, such as `-2` or `-3`. Two names count as the same if they differ only in upper and lower case. The runner logs the new folder name when this happens.\n\n**Why**\n\nOn filesystems that ignore letter case, two repositories such as `Tools` and `tools` would otherwise land in the same folder, and one checkout would overwrite the other. The numbered names keep each checkout separate.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}