@gitset-dev/cli 2.5.0 → 2.5.1

package/README.md

@@ -101,7 +101,7 @@ gitset knowledge init       # scaffold optional .gitset-knowledge.json (include/
 gitset knowledge scan       # zero AI calls — discovers files, prints the plan + exact cost estimate
 gitset knowledge generate   # shows the estimate again, asks to confirm, then writes the knowledge base
 gitset knowledge update     # incremental — only changed modules (and their direct importers) are re-summarized
-gitset knowledge automate   # writes a GitHub Actions workflow that runs `update` in CI and opens a review PR
+gitset knowledge automate   # writes a GitHub Actions workflow that keeps it fresh in CI (direct commits, or PRs with --sync pr)
 ```
 
 It's a six-stage local pipeline (Discover → Map → Summarize → Plan → Write →
@@ -113,22 +113,22 @@ generated link, command, and script before anything is written to disk.
 Secrets are redacted locally before any file content is sent, and prose
 docs / test file bodies are listed structurally but never sent at all.
 
-`gitset knowledge automate` needs "Allow GitHub Actions to create and
-approve pull requests" enabled (**Settings > Actions > General > Workflow
-permissions**) for the update PR to open. It detects this automatically and
-offers to enable it via the GitHub API — asked first, like everything else
-in this command. If you decline, or the API call fails (no admin access, an
-org policy locking the setting), the scheduled update still runs and
-commits safely; only the review-PR step fails, and the workflow run shows
-that failure clearly rather than hide it.
-
-Some organizations enforce that setting off with no repo-level override at
-all — the checkbox greys out even on the org's own settings page. For that
-case, add a repository secret named `GITSET_PR_TOKEN` with a personal
-access token (classic: `repo` scope; fine-grained: Pull requests write).
-It's not subject to that organization-wide Actions restriction, and the
-generated workflow picks it up automatically — no need to re-run `automate`
-or touch the workflow file.
+`gitset knowledge automate` applies updates in one of two ways, and you
+never touch a GitHub settings page for either:
+
+- **Direct commit (the default).** CI commits refreshed docs straight to
+  your default branch using only the built-in Actions token — works on
+  every repository and organization, zero extra permissions or tokens,
+  and it can't re-trigger itself.
+- **Review pull request (`--sync pr`).** Each update arrives as a PR on
+  the `gitset/knowledge-update` branch. Its one prerequisite is set up
+  for you: the CLI first tries enabling the repo's Actions PR permission
+  via the API; if your organization blocks that, it offers to store a
+  token from your existing `gh` login as the `GITSET_PR_TOKEN` secret —
+  explained in plain language before asking, reversible anytime by
+  deleting the secret. If neither works out, updates still commit and
+  push their branch safely; only the PR step fails, and the workflow run
+  shows that failure clearly rather than hide it.
 
 ## Templates
 

package/lib/cli-commit.js

@@ -4,6 +4,11 @@
  * `gitset commit` — local, BYOAI commit-message generation with iterative
  * refinement. No backend, key never leaves the machine.
  *
+ * If nothing is staged but the working tree has changes, an interactive
+ * session is offered a one-time prompt to stage everything (`git add -A`)
+ * and continue; a non-interactive session (CI, `--yes`, `--json`, `--print`,
+ * or no TTY) fails immediately instead of hanging on the prompt.
+ *
  * Flags:
  *   --provider <name>   override default provider for this run
  *   --model <name>      override model
@@ -65,8 +70,44 @@ async function runCommitCommand(argv) {
     return 1;
   }
   if (!changes.diff.trim()) {
-    errln('Nothing staged. Stage changes with `git add` (or pass --all).');
-    return 1;
+    if (nonInteractive) {
+      errln('Nothing staged. Stage changes with `git add` (or pass --all).');
+      return 1;
+    }
+
+    let status = '';
+    try {
+      status = execFileSync('git', ['status', '--porcelain'], { encoding: 'utf8' }).trim();
+    } catch {
+      // getStagedChanges() already confirmed this is a git repo; treat as no changes.
+    }
+    if (!status) {
+      errln('Nothing to commit — the working tree is clean.');
+      return 1;
+    }
+
+    out(theme.warn('No staged changes detected.'));
+    const stage = (await ask('Stage all changes and continue? [y/N] ')).toLowerCase();
+    if (stage !== 'y' && stage !== 'yes') {
+      out('Aborted. Nothing staged.');
+      return 0;
+    }
+    try {
+      execFileSync('git', ['add', '-A'], { stdio: 'ignore' });
+    } catch {
+      errln('`git add -A` failed — is this a git repository?');
+      return 1;
+    }
+    try {
+      changes = getStagedChanges();
+    } catch (e) {
+      errln(e.message);
+      return 1;
+    }
+    if (!changes.diff.trim()) {
+      errln('Still nothing staged after `git add -A` — nothing to commit.');
+      return 1;
+    }
   }
 
   const style = getFlag(argv, '--style') || 'conventional';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gitset-dev/cli",
-  "version": "2.5.0",
+  "version": "2.5.1",
   "description": "Gitset CLI — drafts commits, PRs, issues, READMEs and release notes with your own AI key. Fully local: your code and keys never touch a Gitset server. Draft. Refine. Ship.",
   "type": "commonjs",
   "bin": {