jj-octo 0.9.0 → 0.9.2
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 +4 -2
- package/dist/jj-octo.js +1064 -707
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -42,10 +42,10 @@ With `jj-octo.github-auth` set to `git-proxy`, it sends a placeholder token inst
|
|
|
42
42
|
|
|
43
43
|
A Claude Code [cloud session](https://code.claude.com/docs/en/claude-code-on-the-web) runs in an Anthropic-hosted environment, or in your organization's self-hosted environment. Each needs its own setup.
|
|
44
44
|
|
|
45
|
-
The session's GitHub proxy can append a "Generated by Claude Code" footer to each pull request body that it creates or edits. `jj gh submit` would read the footer as an edit made on GitHub, and write it into the change.
|
|
45
|
+
The session's GitHub proxy can append a "Generated by Claude Code" footer to each pull request body that it creates or edits. `jj gh submit` would read the footer as an edit made on GitHub, and write it into the change. So where `CLAUDE_CODE_REMOTE` is `true`, as in a cloud session, `submit` leaves the footer out when it compares a pull request's body with its change's description. `jj-octo.ignore-claude-code-footer` overrides that: set it to `true` to leave the footer out elsewhere, or to `false` to keep it in a cloud session:
|
|
46
46
|
|
|
47
47
|
```
|
|
48
|
-
jj config set --repo jj-octo.ignore-claude-code-footer
|
|
48
|
+
jj config set --repo jj-octo.ignore-claude-code-footer false
|
|
49
49
|
```
|
|
50
50
|
|
|
51
51
|
### In an Anthropic-hosted environment
|
|
@@ -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.
|