git-coco 0.41.1 → 0.41.2

package/dist/index.esm.mjs

@@ -53,7 +53,7 @@ import { pathToFileURL } from 'url';
 /**
  * Current build version from package.json
  */
-const BUILD_VERSION = "0.41.1";
+const BUILD_VERSION = "0.41.2";
 
 const isInteractive = (config) => {
     return config?.mode === 'interactive' || !!config?.interactive;
@@ -6750,13 +6750,35 @@ async function getCommitLogRangeDetails(from, to, { noMerges, git }) {
 }
 
 /**
- * Retrieves the name of the current branch.
+ * Retrieve the name of the current branch.
  *
- * @param {GetCurrentBranchName} options - The options for retrieving the branch name.
- * @returns {Promise<string>} - A promise that resolves to the name of the current branch.
+ * The first-choice path uses `git rev-parse --abbrev-ref HEAD`, which
+ * returns the active branch on a normal repo. On an initial-commit
+ * repo (fresh `git init` with no commits yet) HEAD does not resolve
+ * and rev-parse fails fatally — but `git symbolic-ref --short HEAD`
+ * still reports the configured initial branch name, so we fall
+ * through to that. Final fallback is an empty string for genuinely
+ * detached / corrupt states; every caller treats that as "no branch
+ * context", which is the right semantics for a no-HEAD repo.
+ *
+ * Without this resilience, every command that depends on the branch
+ * name (e.g. the post-summary step in `coco commit`) would crash
+ * with `fatal: ambiguous argument 'HEAD'` after the entire diff
+ * pipeline already ran (#844).
  */
 async function getCurrentBranchName({ git }) {
-    return await git.revparse(['--abbrev-ref', 'HEAD']);
+    try {
+        return await git.revparse(['--abbrev-ref', 'HEAD']);
+    }
+    catch {
+        try {
+            const ref = await git.raw(['symbolic-ref', '--short', 'HEAD']);
+            return ref.trim();
+        }
+        catch {
+            return '';
+        }
+    }
 }
 
 /**

package/dist/index.js

@@ -78,7 +78,7 @@ var readline__namespace = /*#__PURE__*/_interopNamespaceDefault(readline);
 /**
  * Current build version from package.json
  */
-const BUILD_VERSION = "0.41.1";
+const BUILD_VERSION = "0.41.2";
 
 const isInteractive = (config) => {
     return config?.mode === 'interactive' || !!config?.interactive;
@@ -6775,13 +6775,35 @@ async function getCommitLogRangeDetails(from, to, { noMerges, git }) {
 }
 
 /**
- * Retrieves the name of the current branch.
+ * Retrieve the name of the current branch.
  *
- * @param {GetCurrentBranchName} options - The options for retrieving the branch name.
- * @returns {Promise<string>} - A promise that resolves to the name of the current branch.
+ * The first-choice path uses `git rev-parse --abbrev-ref HEAD`, which
+ * returns the active branch on a normal repo. On an initial-commit
+ * repo (fresh `git init` with no commits yet) HEAD does not resolve
+ * and rev-parse fails fatally — but `git symbolic-ref --short HEAD`
+ * still reports the configured initial branch name, so we fall
+ * through to that. Final fallback is an empty string for genuinely
+ * detached / corrupt states; every caller treats that as "no branch
+ * context", which is the right semantics for a no-HEAD repo.
+ *
+ * Without this resilience, every command that depends on the branch
+ * name (e.g. the post-summary step in `coco commit`) would crash
+ * with `fatal: ambiguous argument 'HEAD'` after the entire diff
+ * pipeline already ran (#844).
  */
 async function getCurrentBranchName({ git }) {
-    return await git.revparse(['--abbrev-ref', 'HEAD']);
+    try {
+        return await git.revparse(['--abbrev-ref', 'HEAD']);
+    }
+    catch {
+        try {
+            const ref = await git.raw(['symbolic-ref', '--short', 'HEAD']);
+            return ref.trim();
+        }
+        catch {
+            return '';
+        }
+    }
 }
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "git-coco",
-  "version": "0.41.1",
+  "version": "0.41.2",
   "description": "zero-effort git commits with coco.",
   "author": "gfargo <ghfargo@gmail.com>",
   "license": "MIT",