From 312c37be25d77e9d48868325bcc49050e1b2dbdc Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 23 Mar 2026 21:33:29 +0000 Subject: [PATCH] fix: correct extension registry path in specify.md template Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com> Agent-Logs-Url: https://github.com/github/spec-kit/sessions/809a1dbf-1301-4312-b4d2-e18f9b3e8b2f --- templates/commands/specify.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/templates/commands/specify.md b/templates/commands/specify.md index d5afd740..53787618 100644 --- a/templates/commands/specify.md +++ b/templates/commands/specify.md @@ -76,10 +76,10 @@ Given that feature description, do this: 2. **Create the feature branch** by running the script with `--short-name` (and `--json`). In sequential mode, do NOT pass `--number` — the script auto-detects the next available number. In timestamp mode, the script generates a `YYYYMMDD-HHMMSS` prefix automatically: **Git extension check**: Before running the branch creation script, check if the git extension is enabled: - - Check if `.specify/extensions/.registry/git.json` exists - - If it exists, read it and verify `"enabled"` is `true` (or not explicitly set to `false`) - - If the git extension is **disabled** or the registry file does not exist, **skip branch creation entirely** — proceed directly to step 3 using a spec directory name derived from the short name (e.g., `specs//`) - - If the git extension is enabled (or the registry file doesn't exist but `.specify/init-options.json` has `branch_numbering` set), proceed with branch creation below + - Check if `.specify/extensions/.registry` exists (a single JSON file tracking all extensions) + - If it exists, read the JSON and look for `extensions.git`; verify its `"enabled"` field is `true` (or not explicitly `false`) + - If the git extension is **disabled** (explicitly `"enabled": false`), **skip branch creation entirely** — proceed directly to step 3 using a spec directory name derived from the short name (e.g., `specs//`) + - If the registry file does not exist, proceed with branch creation using the default behavior (backward compatibility) **Branch numbering mode**: Before running the script, determine the branch numbering strategy: 1. Check `.specify/extensions/git/git-config.yml` for `branch_numbering` value (extension config takes precedence)