{"version":"2.1.281","anchor":"batch-works-outside-a-git-repository-when-a-worktreecreate","canonical_anchor":"batch-works-outside-a-git-repository-when-a-worktreecreate","heading":"\/batch works outside a git repository when a WorktreeCreate hook is configured","tier":"use","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/batch-works-outside-a-git-repository-when-a-worktreecreate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### \/batch works outside a git repository when a WorktreeCreate hook is configured\n\n`\/batch` now runs outside a git repository when a `WorktreeCreate` hook is configured, publishing through the project's own version control\n\n**What**\n\n`\/batch` splits a large change across several workers, each in its own worktree, a separate working copy of the project. It no longer needs git. It now refuses only when the directory is not in a git repository and no `WorktreeCreate` hook (a user-set command that creates worktrees) is configured, and says so in a new message.\n\nWhen worktrees come from the hook instead of git, a \"Version control\" section is added to the batch instructions. It tells the model:\n\n- `git` and `gh` commands will not work.\n\n- Each worker should replace the commit, push and pull request step with the project's own version-control commands.\n\n- A worker that reports `PR: none` along with what it published instead counts as done.\n\n**Why**\n\nProjects that use a version-control system other than git can use `\/batch` by providing a `WorktreeCreate` hook.\n\n- Area: Slash Commands\n- Names: `\/batch`, `WorktreeCreate`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}