@withandeo/cli 0.18.0 → 0.19.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +26 -0
- package/dist/api.d.ts +22 -1
- package/dist/api.d.ts.map +1 -1
- package/dist/api.js +17 -0
- package/dist/api.js.map +1 -1
- package/dist/contracts.d.ts +31 -0
- package/dist/contracts.d.ts.map +1 -1
- package/dist/git-outcome.d.ts +32 -0
- package/dist/git-outcome.d.ts.map +1 -0
- package/dist/git-outcome.js +111 -0
- package/dist/git-outcome.js.map +1 -0
- package/dist/main.d.ts.map +1 -1
- package/dist/main.js +105 -2
- package/dist/main.js.map +1 -1
- package/package.json +1 -1
- package/skill/tender-accounts/references/managed-source.md +22 -0
|
@@ -62,6 +62,28 @@ npx @withandeo/cli source log --branch main --limit 20 --json
|
|
|
62
62
|
npx @withandeo/cli source compare --base main --head feature/account-copy --json
|
|
63
63
|
```
|
|
64
64
|
|
|
65
|
+
For a historical branch that missed automatic post-landing cleanup, a merchant
|
|
66
|
+
source administrator may use the guarded deletion workflow. First confirm the
|
|
67
|
+
exact head and compare it to the authoritative default, then dry-run:
|
|
68
|
+
|
|
69
|
+
```sh
|
|
70
|
+
npx @withandeo/cli source branch delete \
|
|
71
|
+
--branch feature/account-copy \
|
|
72
|
+
--expected-head <exact-head-sha> \
|
|
73
|
+
--dry-run --json
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
Apply only when the dry run reports `eligible`, using the returned repository
|
|
77
|
+
ID as the confirmation and a stable idempotency key. Andeo retains moved,
|
|
78
|
+
unmerged, protected, default, provider-default, or in-use refs. Never replace
|
|
79
|
+
this workflow with a raw write token or `git push --delete`. The operation
|
|
80
|
+
affects only the hosted branch ref and never local GitButler state or production.
|
|
81
|
+
Applying also requires completed managed Git gateway cutover with legacy provider
|
|
82
|
+
credentials revoked. `source_transport_uncontrolled` retains the branch until
|
|
83
|
+
that separate operator workflow is complete. Pending or unknown gateway writes
|
|
84
|
+
to the candidate or recorded default must be investigated; acknowledging an
|
|
85
|
+
incident does not make an uncertain provider mutation safe to delete around.
|
|
86
|
+
|
|
65
87
|
Use standalone source-administration commands only for repositories where
|
|
66
88
|
reviewed changes are not enabled and when the user explicitly requests a
|
|
67
89
|
default-branch or history change and the active profile belongs to a merchant
|