jj-octo 0.9.1 → 0.9.3
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 +3 -1
- package/dist/jj-octo.js +1282 -802
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -28,7 +28,7 @@ mise use --global github:kkom/jj-octo@X.Y.Z
|
|
|
28
28
|
|
|
29
29
|
Then run `jj-octo init` once in each checkout. It makes the checkout a jj repository colocated with git, makes GitHub's default branch `trunk()`, and sets the `jj gh` alias.
|
|
30
30
|
|
|
31
|
-
|
|
31
|
+
`init` records its version in the repository's jj config, as `jj-octo.set-up-version`. Every other command except `doctor` runs `init` first where an older version is recorded, or none is. So after an upgrade, the first command sets up what the new version needs. `jj-octo doctor` reports what isn't set up, and changes nothing.
|
|
32
32
|
|
|
33
33
|
## GitHub access
|
|
34
34
|
|
|
@@ -75,3 +75,5 @@ bun run fix # format and lint fixes
|
|
|
75
75
|
```
|
|
76
76
|
|
|
77
77
|
To release, run `bun run release:patch`, `release:minor` or `release:major` in a pull request, which raises `version` in `package.json`. Once it is merged and the checks pass on `main`, the same workflow publishes that version to npm, and as a GitHub release with the executables.
|
|
78
|
+
|
|
79
|
+
The workflow publishes the version from the last commit of the push. So merge a release pull request with nothing above it: in a stack, run `jj gh merge -r` on the release change, then merge the pull requests above it. Until the release is merged, the `CI` check fails on each pull request above it. `main` requires `CI` to pass, so GitHub doesn't merge those pull requests with the release.
|