@myna-sh/cli 0.11.0 → 0.12.1
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 +24 -0
- package/dist/main.js +530 -162
- package/dist/main.js.map +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -64,6 +64,30 @@ myna changes diff chs_...
|
|
|
64
64
|
|
|
65
65
|
Run `myna --help` or `myna <command> --help` for the complete command reference. Global flags include `--json`, `--organization`, `--project`, `--token`, and `--api-url`.
|
|
66
66
|
|
|
67
|
+
## Pin content to a release
|
|
68
|
+
|
|
69
|
+
`myna.lock` records the release a repository builds against, so the same commit
|
|
70
|
+
builds the same site. `myna pull` moves it.
|
|
71
|
+
|
|
72
|
+
```sh
|
|
73
|
+
myna pull # pin to the newest release
|
|
74
|
+
myna pull --release 42 # pin to a specific one
|
|
75
|
+
myna pull --check # non-zero exit when the pin is behind (for CI)
|
|
76
|
+
myna pull --open-pr # bump on a branch and open a pull request
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
`--open-pr` writes a pull request whose body is the field-level diff of every
|
|
80
|
+
release being taken on, so CI runs the real build against the new content before
|
|
81
|
+
anyone merges it. It needs `git` and the GitHub CLI. Read the pin with
|
|
82
|
+
`readLock()` from `@myna-sh/sdk/lock` and pass it to `createMyna({ release })`.
|
|
83
|
+
|
|
84
|
+
Add `--run` when the repository generates something from content, and the
|
|
85
|
+
regenerated artifact is committed with the pin that produced it:
|
|
86
|
+
|
|
87
|
+
```sh
|
|
88
|
+
myna pull --open-pr --run 'pnpm build:content'
|
|
89
|
+
```
|
|
90
|
+
|
|
67
91
|
## Environment
|
|
68
92
|
|
|
69
93
|
```text
|