@mediamonks/canopy-cli 0.7.31 → 0.7.33

package/dist/skill/canopy/SKILL.md

@@ -104,6 +104,11 @@ and never go stale.
 - Work bug reports & feedback: `canopy feedback list | show | comment | status | report`
   — see [Working feedback reports](#working-feedback-reports-issues) below
 - CI credentials: `canopy token create | list | revoke`
+- Git: `canopy repo show --json` (is there a repository, and its remote) ·
+  `canopy repo create` · `canopy repo clone <slug>` · `canopy repo connect`
+  (set up an existing folder). Then plain `git`: the CLI gives git
+  short-lived credentials itself, so never ask for, paste or store a git
+  token. Pushing doesn't deploy — `canopy deploy` does.
 
 ## Working feedback reports (issues)
 
@@ -183,7 +188,8 @@ Non-interactive: `canopy create "My App" --template spa`. **When unsure between
 
 ## Safety rules
 
-- **Destructive commands** — `canopy db restore` and `canopy delete` wipe data.
+- **Destructive commands** — `canopy db restore`, `canopy delete` and
+  `canopy repo delete` (the project's git history) wipe data.
   Confirm intent with the user first, and take a `canopy db snapshot` before
   restores.
 - **Deploys are public.** `canopy deploy` makes a version live. Confirm before

package/dist/{skill-BWmXiJAz.mjs → skill-Dg7dQF0k.mjs}

@@ -1,4 +1,4 @@
-import { t as version } from "./package-CiKTWo0_.mjs";
+import { t as version } from "./package-CQIPmdcO.mjs";
 import { r as reportErrors } from "./ui-C_jSc1Kz.mjs";
 import { defineCommand } from "citty";
 import { cpSync, existsSync, mkdirSync, rmSync, symlinkSync, writeFileSync } from "node:fs";

package/dist/templates/spa/AGENTS.md

@@ -35,6 +35,19 @@ the [Canopy dashboard](https://dashboard.thanarie.dev).
   `canopy promote` ships the exact tested version. Never promote with failing
   checks.
 
+## Git
+
+Code can live in a git repository Canopy keeps for the project (no GitHub
+account needed). `canopy repo show --json` says whether there is one and gives
+its remote; `canopy repo create` makes one, `canopy repo clone <slug>` or
+`canopy repo connect` sets a folder up. After that it is plain `git` — the CLI
+hands git short-lived credentials by itself:
+
+- Never ask for, paste or store a git token or password.
+- Pushing doesn't deploy — `canopy deploy` still does.
+- The `.github/workflows` file here only runs on GitHub; on a Canopy
+  repository it is kept but never runs.
+
 ## Boundaries
 
 - Do not add auth — the platform authenticates every request before it

package/dist/templates/spa/_gitignore

@@ -2,3 +2,7 @@ node_modules/
 dist/
 .canopy/
 .DS_Store
+# Local secrets never go into git (secrets belong in `canopy secrets`).
+.dev.vars
+.env*
+!.env.example

package/dist/templates/static/AGENTS.md

@@ -34,6 +34,17 @@ the [Canopy dashboard](https://dashboard.thanarie.dev).
   `canopy promote` ships the exact tested version. Never promote with failing
   checks.
 
+## Git
+
+Code can live in a git repository Canopy keeps for the project (no GitHub
+account needed). `canopy repo show --json` says whether there is one and gives
+its remote; `canopy repo create` makes one, `canopy repo clone <slug>` or
+`canopy repo connect` sets a folder up. After that it is plain `git` — the CLI
+hands git short-lived credentials by itself:
+
+- Never ask for, paste or store a git token or password.
+- Pushing doesn't deploy — `canopy deploy` still does.
+
 ## Boundaries
 
 - Do not add auth — the platform authenticates every request before it

package/dist/templates/static/_gitignore

@@ -1,2 +1,6 @@
 .canopy/
 .DS_Store
+# Local secrets never go into git (secrets belong in `canopy secrets`).
+.dev.vars
+.env*
+!.env.example

package/dist/templates/worker/AGENTS.md

@@ -51,6 +51,19 @@ the [Canopy dashboard](https://dashboard.thanarie.dev).
   `canopy promote` ships the exact tested version. Never promote with failing
   checks.
 
+## Git
+
+Code can live in a git repository Canopy keeps for the project (no GitHub
+account needed). `canopy repo show --json` says whether there is one and gives
+its remote; `canopy repo create` makes one, `canopy repo clone <slug>` or
+`canopy repo connect` sets a folder up. After that it is plain `git` — the CLI
+hands git short-lived credentials by itself:
+
+- Never ask for, paste or store a git token or password.
+- Pushing doesn't deploy — `canopy deploy` still does.
+- The `.github/workflows` file here only runs on GitHub; on a Canopy
+  repository it is kept but never runs.
+
 ## Boundaries
 
 - Do not add auth — the platform authenticates every request before it

package/dist/templates/worker/_gitignore

@@ -3,3 +3,6 @@ dist/
 .canopy/
 .dev.vars
 .DS_Store
+# Local secrets never go into git (secrets belong in `canopy secrets`).
+.env*
+!.env.example

package/dist/{upgrade-Cexs9KYX.mjs → upgrade-huJDjhrV.mjs}

@@ -112,7 +112,7 @@ const upgradeCommand = defineCommand({
 		const spec = `${PACKAGE_NAME}@${args.version ?? "latest"}`;
 		const command = pmCommand(pm);
 		const cmd = installArgs(pm, spec);
-		const { skillInstalled } = await import("./skill-BWmXiJAz.mjs");
+		const { skillInstalled } = await import("./skill-Dg7dQF0k.mjs");
 		const { homedir } = await import("node:os");
 		const refreshGlobal = skillInstalled(homedir());
 		const refreshRepo = process.cwd() !== homedir() && skillInstalled(process.cwd());

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mediamonks/canopy-cli",
-  "version": "0.7.31",
+  "version": "0.7.33",
   "description": "Canopy CLI — create, develop and deploy Canopy projects.",
   "bin": {
     "canopy": "./dist/index.mjs"
@@ -27,6 +27,7 @@
   },
   "devDependencies": {
     "@types/node": "^26.1.1",
+    "ai": "^7.0.82",
     "typescript": "^7.0.2",
     "vite-plus": "0.2.5",
     "@mediamonks/canopy-pages": "0.0.0"